search

gcode-mirror / google-highly-open-participation-drupal

Automatically exported from code.google.com/p/google-highly-open-participation-drupal
0 stars 0 forks source link

Simpletests for Actions and Triggers #124

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Creating a workflow with the actions and triggers system
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.

Your overall task will be to create an ActionsTestCase class which would 
be the basis for all actions/triggers test cases.  The first step of the 
task will be to evaluate functions that would be useful in an ActionsTestCase.
Compile a list of at least ten (10) functions that might be useful for the
ActionsTestCase.  Next, you will create the easily extendable class, with
all of the functions proposed (through in a few more for kicks if you want).
Last, you must make five (5) tests that extend the ActionsTestCase, to
demonstrate the usage of the new class.

Resources:
http://drupal.org/simpletest
http://drupal.org/project/simpletest
http://www.lullabot.com/articles/introduction-unit-testing
http://cwgordon.com/the-power-of-drupal-simpletests-and-the-simpletest-revolutio
n

Original issue reported on code.google.com by dmitri...@gmail.com on 31 Dec 2007 at 5:52

GoogleCodeExporter commented 9 years ago 
I claim this task.

Original comment by cwgord...@cwgordon.com on 31 Dec 2007 at 5:53

GoogleCodeExporter commented 9 years ago 
cwgord...@yahoo.com, task is yours (done task hopping? j/k ;-))

Please post all work to the Drupal issue: http://drupal.org/node/205157

Original comment by addi.be...@gmail.com on 31 Dec 2007 at 6:03

GoogleCodeExporter commented 9 years ago 
Needs review

Original comment by cwgord...@cwgordon.com on 6 Jan 2008 at 7:51

Attachments:

GoogleCodeExporter commented 9 years ago 
Marking as needs review.

Original comment by acli...@gmail.com on 6 Jan 2008 at 3:32

GoogleCodeExporter commented 9 years ago 
Shouldn't all the actions be prefixed with triggers_, not trigger_.
Another comment - you're testing various actions.  What happened to testing 
triggers too?

Original comment by dmitri...@gmail.com on 6 Jan 2008 at 4:54

GoogleCodeExporter commented 9 years ago 
Ok, new version attached.

Original comment by cwgord...@cwgordon.com on 6 Jan 2008 at 8:58

Attachments:

GoogleCodeExporter commented 9 years ago 
Reviewed - looks good!

Original comment by dmitri...@gmail.com on 6 Jan 2008 at 9:00

GoogleCodeExporter commented 9 years ago

Original comment by acli...@gmail.com on 21 Jan 2008 at 3:58