suggested task writeup:
Summary: Write Simpletest tests for admin/build/modules functionality
Having a full suite of tests for Drupal 6.x core functionality using the Simpletest module would be a major step forward for the project to insure that new code does not introduce bugs into basic functionality.
For this task, you need to first install and familiarize yourself with the simpletest module (use the cvs HEAD version with Drupal HEAD/6.x Beta):
http://drupal.org/project/simpletest
http://drupal.org/simpletest
The main work for this task is to write a small suite of tests to check the basic functionality at admin/build/modules. This suite should be written as a single .test file.
Suggested tests:
1. Enable all core modules by POST - look for error messages, confirm table creation, etc.
2. Attempt to enable a module with non-enabled dependencies, for example by disabling comment and enabling forum. Use POST. Confirm expected error message and that module is not enabled.
3. Disable and uninstall a module (such as aggregator) or better all modules enabled in #1. Confirm table deletion, look for error messages, etc.
Comments
Comment #1
pwolanin commentedrevised text
Having a full suite of tests for Drupal 6.x core functionality using the Simpletest module would be a major step forward for the project to insure that new code does not introduce bugs into basic functionality. New core tests will be committed to the Simpletest project and used for automated testing by http://testing.drupal.org.
For this task, you need to first install and familiarize yourself with the simpletest module (use the cvs HEAD version with Drupal HEAD/6.x Beta):
http://drupal.org/project/simpletest
http://drupal.org/simpletest
The main work for this task is to write a small suite of tests to check the basic functionality at admin/build/modules. This suite should be written as a single .test file and should achieve RTBC status in the Simpletest module issue queue.
Suggested tests:
1. Enable all core modules by POST - look for error messages, confirm table creation, etc.
2. Attempt to enable a module with non-enabled dependencies, for example by disabling comment and enabling forum. Use POST. Confirm expected error message and that module is not enabled.
3. Disable and uninstall a module (such as aggregator) or better all modules enabled in #1. Confirm table deletion, look for error messages, etc.
Comment #2
cwgordon7 commentedMy feedback:
1) Just reading this post confuses me. After reading the post several times, looking at the links, and asking questions on irc, I think I understand most of it; however, the description needs to be a lot clearer about what this task (and simpletest itself) actually IS.
2) Otherwise looks fascinating: simpletest looks like a great, fun, interesting thing to work on. Just reword the description.
-cwgordon7
Comment #3
webchickFYI: cwgordon7 is one of our actual GHOP students, so I value his feedback very much.
Write a nice "What is SimpleTest and why should I care?" paragraph to go at the beginning, and I think all three of these are good to go.
Comment #4
pwolanin commentedfurther revised text
Enabling and disabling modules is a key administrative task for any Drupal site. However, would you manually check each new patch to insure that it does not break some part of this functionality?
The Simpletest module provides a framework for running automated unit tests in Drupal. Unit testing involves taking a small portion of code, a unit, and subjecting it to programmatic tests to prove its correctness. This can be extremely useful to help insure that new code does not introduce bugs into existing functionality. Thus, having a full suite of unit tests for Drupal 6.x core functionality using the Simpletest module would be a major step forward for the project and would help insure that only high-quality code is committed. In addition to helping developers test their code, new tests for core Drupal functionality will be used for automated testing by http://testing.drupal.org.
For this task, you need to first install and familiarize yourself with the simpletest module (use the cvs HEAD version with Drupal HEAD/6.x Beta):
http://drupal.org/project/simpletest
http://drupal.org/simpletest
http://www.lullabot.com/articles/introduction-unit-testing
The main work for this task is to write a small suite of tests to check the basic functionality at admin/build/modules. This suite should be written as a single .test file and should achieve RTBC status in the Simpletest module issue queue.
Suggested tests:
1. Enable all core modules by POST - look for error messages, confirm table creation, etc.
2. Attempt to enable a module with non-enabled dependencies, for example by disabling comment and enabling forum. Use POST. Confirm expected error message and that module is not enabled.
3. Disable and uninstall a module (such as aggregator) or better all modules enabled in #1. Confirm table deletion, look for error messages, etc.
Comment #5
webchickAs said on IRC, looks great. :) I like that the sentence on the top is easily changed and can help to tell the difference between the various SimpleTest tasks.
Go ahead and taskify this and the other two when you get a chance.
Comment #6
pwolanin commentedposted task: http://code.google.com/p/google-highly-open-participation-drupal/issues/...
Comment #7
webchickCool. Marking closed to take out of listings.