Diagram of automated testing process

The feedback on this diagram is that it was not proper. We need to update it. We also need to better reflect integration with project issue file testing and other systems.

This is a blocker.

I have updated the diagram.

- In the diagram what is 'Test_it'? Is that to test whether the patch
applies or not? If so, it might be worth renaming for clarity.

- 'run_all_tests' means 'Run all simpletests'?

- What is 'Drupalchk' and how is it different from 'Test_it'? I'd
make this more verbose -- i.e. change the name of the script by a
short 3-5 word sentence like you do elsewhere (i.e. 'Checkout Drupal
from CVS'). Right now, I have to guess what 'Test_it' and 'Drupalchk'
does. I'd prefer not to guess.

- The names of the scripts look inconsistent. Some use camel casing
other use dashed and underscores. Probably best to use dashes
everywhere. Better yet to remove script names from the diagram. See
also my point above.

- The legend seems incomplete. Two symbols are missing. Not a big
deal but I figured I'd point it out.

- Sometimes the word 'queue' is ambiguous. There is a 'patch queue'
and there is an 'issue queue'.

- Is a 'User' a 'Bug reporter'?

- The 'User workflow' should probably come above the 'Contributor
workflow'. The former is more common and easier to grok.

- The font of the roadmap mindmap is too small and blurry. Can we
make it a tad larger and more crisp? I'd love to be able to read it. ;)

Ok, added a link to the detailed larger version. http://testing.drupal.org/files/test-driven-development-drupal.jpeg

- In the diagram what is 'Test_it'? Is that to test whether the patch
applies or not? If so, it might be worth renaming for clarity.

- 'run_all_tests' means 'Run all simpletests'?

Yes, updated.

- What is 'Drupalchk' and how is it different from 'Test_it'? I'd
make this more verbose -- i.e. change the name of the script by a
short 3-5 word sentence like you do elsewhere (i.e. 'Checkout Drupal
from CVS'). Right now, I have to guess what 'Test_it' and 'Drupalchk'
does. I'd prefer not to guess.

I have changed some of the names to be more descriptive.

- The names of the scripts look inconsistent. Some use camel casing
other use dashed and underscores. Probably best to use dashes
everywhere. Better yet to remove script names from the diagram. See
also my point above.

All changed to dashes or made into phrases. No underscores are used.

- The legend seems incomplete. Two symbols are missing. Not a big
deal but I figured I'd point it out.

Legends updated on both diagrams.

- Sometimes the word 'queue' is ambiguous. There is a 'patch queue'
and there is an 'issue queue'.

Updated both.

- Is a 'User' a 'Bug reporter'?

No. Just someone looking at an issue.

- The 'User workflow' should probably come above the 'Contributor
workflow'. The former is more common and easier to grok.

done.

- It would be useful to include a link to the simpletest project
somewhere. Where can one see or explore these tests?

On home page. Done.

- It would be useful to show what happens when a test fails, and to
show what happens when a test succeeds. Right now, we're only
returning 'Results' but how are these results used? From the diagram
it looks as if they are stored in the 'test results table' but what
does that mean? Is it visualized in the issue? Is it used to alter
the issue's status? Is it used to notify someone? It's strikes me as
critical information for mere mortals ...

http://testing.drupal.org/examples. done.