I've been working away at a Drupal 6 module that will automate the process of performing a Drupal cvs checkout, installation and testing against core. The intent of this module is to be used on http://testing.drupal.org/ ... I was able to get the checkout and simpletest based installation working up to the point where the JS generated progress bar starts. There is a redirect in place that I believe is generated from the Batch API that does not play well with simpletest. As such, using simpletest to perform an installation currently does not seem to be possible. The details of the problem are outlined in two tickets that I have found.
http://drupal.org/node/204374 has been marked as a duplicate of http://drupal.org/node/229905 ... reading both issues helps understand the problem as it relates to writing a simpletest based installation.
I am in search of feedback/ideas on how to progress with this issue.
Comments
I think Rok Žlender was
I think Rok Žlender was working on something like this. You may want to confer with him.
Rok worked around this with
Rok worked around this with a 1 second pause in a loop http://testing.drupal.org/viewvc/simpletestauto/install_drupal.inc ... thanks!
Can you explain this more thoroughly?
I've been not doing much d6/d7 patch testing because my download/patch/install scripts were breaking on the new installer for this reason. I don't quite understand what the one second pause does, and I've been unable to replicate the desired results using curl or wget.
Is it possible that the testing framework be used for this type of stuff just for a single developer to automate their workflow?
If so are there any docs, or info out there?
The problem, as I understand
The problem, as I understand it, is a redirect in the batch api that is structured in such a way that the simpletest browser fails at the bit where you see an AJAX-ified progress bar. Taking a look at http://testing.drupal.org/viewvc/simpletestauto/install_drupal.inc?view=... gives you each of the base classes you need to use simpletest in relation to installations. In the class TestDrupal6Install you will find the following snippet created by Rok:
$this->assertResponse(200);
$this->assertTitle(new PatternExpectation('/Installing Drupal/'));
$i = 0;
do { $gotopath = $args->install_url . $args->instance . '/install.php?locale=en&profile=default&id=1&op=do_nojs';
$this->assertTrue($this->get($gotopath));
$this->assertResponse(200);
$res = strpos($this->_browser->getContent(), 'Remaining 0 of 10');
$i++;
} while ($res === FALSE && $i < 5);
$gotopath = $args->install_url . $args->instance . '/install.php?locale=en&profile=default&id=1&op=finished';
$this->assertTrue($this->get($gotopath));
$this->assertResponse(200);
This snippet checks for the correct response code from filling in the db settings form then enters into a loop that checks for the text "Remaining 0 of 10" ... at that point the installation is considered complete. Rather than rely on the redirect from the batch api, the simpletest browser is redirected to the next page and checks for a valid response before continuing.
Does that help?
Sorta
I pretty much tried that before, and tried to replicate that as closely as I could, but the second time that I go to fetch '/install.php?locale=en&profile=default&id=1&op=do_nojs' I get a SQL error. It's very odd, as the tables are created in the database, but somehow Drupal is never fully bootstrapped. I've tried to manual recover the install by hitting it in a browser but that is completely stuck, and trying to visit the site homepage results in a php error (call to undefined function, user_access).
So still no dice for my attempts to automate checkout, patching and install.
had this same problem
Please see my post at http://drupal.org/node/210752#comment-1798776 - applying the patch there allowed me to run install.php with curl.
cheers,
Adrian