That SimpleTest error happens when the first test fails. Since the test didn't complete, it's test_id does not get saved. If more than one tests pass, a valid test_id is saved. I have an issue report for this bug at http://drupal.org/node/325824*. * Dave* *
That particular error is usually caused by a bug in one of the unit tests you ran causing simpletest to hiccup. I've seen it a couple of times, and it's sometimes sporadic, unfortunately. It could be a bug in simpletest itself. I've not ruled that out yet.
See if you can narrow it down to a single test that's causing the problem. If you can establish a pattern (a particular test, more than X tests, some particular phase of the moon, etc.) then file a bug report for the appropriate module (which could be simpletest itself). If you need more help narrowing it down, stop by #Drupal on IRC. Simpletest is high in the mind of most core devs of late, so there's a good chance you'll find someone who can give you more detailed help tracking down the problem.
Thank you for helping make Drupal better!
--Larry Garfield
On Thu, 30 Oct 2008 13:16:11 -0400, "Sookocheff, Kevin" <Kevin.Sookocheff@cbsa-asfc.gc.ca> wrote:
Hello,
I had checked out a fresh version of Drupal from CVS this morning and each time I run some SimpleTest test cases I receive the following error:
Undefined index: test_id in _simpletest_batch_finished() (line 423 of E:\xampp\htdocs\drupal_test\modules\simpletest\simpletest.module).
I am new to Drupal development and want to get started by writing some tests and reviewing patches. Does anyone have an idea about fixing the above problem so that I can get started?
Thanks, Kevin