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

Write Simpletest tests for Content translation module #130

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Drupal 6 supports content (node) translation out of the box with the 
included content translation module. This task is to write unit tests to 
ensure this functionality works.

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 RC):
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 functionality of translation module with a test site setup to have at
least two languages and both locale and translation module enabled. The
test case should:
* set the Story content type to be multilanguage enabled with translation
* create a story in one of the languages
* submit a translation of the story in one of the other languages
* update the original story and mark the translation outdated
* update the translation and mark it as up-to-date

Proper validation of your new tests will ideally include changing the
Drupal core code to break the tested functionality and then confirming
that your tests report a failure. Ideally, post each such change as a
patch to help the reviewers.

This suite should be written as a single .test file and should achieve
RTBC status at http://drupal.org/node/207385

Original issue reported on code.google.com by chx1...@gmail.com on 7 Jan 2008 at 9:30

GoogleCodeExporter commented 9 years ago
I forgot to mention: a very very crude start for the tests can be created from 
the 
browser with http://drupal.org/project/simpletest_automator -- generated tests 
need 
serious cleanup and editing.

Also see 
http://www.lullabot.com/articles/drupal-module-developer-guide-simpletest

Original comment by chx1...@gmail.com on 8 Jan 2008 at 2:26

GoogleCodeExporter commented 9 years ago
I claim this task.

Original comment by j.boomba...@gmail.com on 11 Jan 2008 at 11:00

GoogleCodeExporter commented 9 years ago
Awesome. :) Go to town!

Original comment by webchick...@gmail.com on 11 Jan 2008 at 11:12

GoogleCodeExporter commented 9 years ago
Posted submission at http://drupal.org/node/207385.

Original comment by j.boomba...@gmail.com on 12 Jan 2008 at 3:47

GoogleCodeExporter commented 9 years ago

Original comment by pwola...@gmail.com on 12 Jan 2008 at 3:49

GoogleCodeExporter commented 9 years ago
In basically no time student finished this task and made all requested changes 
and
corrections. Maybe we should make things a bit harder :). Great job and thanks. 

Original comment by rok.zlen...@gmail.com on 12 Jan 2008 at 9:47

GoogleCodeExporter commented 9 years ago
j.boombatower:  could you please post your patch(es) for this task here in this
issue, since that's required by google.  Also, can you please go back through 
your
other tasks and make sure to do the same there.  Thanks.

Original comment by acli...@gmail.com on 17 Jan 2008 at 10:27

GoogleCodeExporter commented 9 years ago
Final copy.

Original comment by j.boomba...@gmail.com on 17 Jan 2008 at 10:52

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by acli...@gmail.com on 21 Jan 2008 at 4:05