Closed GoogleCodeExporter closed 9 years ago
Original comment by chx1...@gmail.com
on 7 Jan 2008 at 8:34
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.
Original comment by chx1...@gmail.com
on 7 Jan 2008 at 8:46
I claim this task.
Original comment by j.boomba...@gmail.com
on 8 Jan 2008 at 1:34
Also see
http://www.lullabot.com/articles/drupal-module-developer-guide-simpletest
Original comment by chx1...@gmail.com
on 8 Jan 2008 at 2:24
All yours. :)
Original comment by webchick...@gmail.com
on 8 Jan 2008 at 2:33
Oops. Forgot to change status.
Original comment by webchick...@gmail.com
on 8 Jan 2008 at 3:51
The module test I created tests both the node and administration interfaces for
creating, editing, and deleting path aliases. There are two separate functions:
testAdminAlias, testNodeAlias that perform the tasks described above.
I created separate patches for showing that the tests will catch mistakes in
the path
module. The patches modify lines in the path module that disable the
funtionality
tested by the test case.
The atatched patches end with the suffixes insert, update, and delete refering
to the
functionality that they will disable and allow the test case to catch. The base
attachment, that has no suffix, just adds the test case.
Original comment by j.boomba...@gmail.com
on 8 Jan 2008 at 5:50
Attachments:
I don't see a link to a drupal.org node like the other issues so I just posted
it all
here. Not sure if you are intending to create one or what.
Original comment by j.boomba...@gmail.com
on 8 Jan 2008 at 5:52
Sorry, the issue is http://drupal.org/node/207196 . I am copying over.
Original comment by chx1...@gmail.com
on 8 Jan 2008 at 7:58
I copied over the file and commented there.
Original comment by chx1...@gmail.com
on 8 Jan 2008 at 8:30
I'm setting this to needs review.
Original comment by acli...@gmail.com
on 8 Jan 2008 at 12:07
I gave a review already.
Original comment by chx1...@gmail.com
on 8 Jan 2008 at 12:17
@chx: I know you gave a review already, but we've mostly been setting the
google
tasks to needs review once there's something to review at all, even if the
student's
work needs to be revised, and we leave it as needs review until either time
runs out
or the student finishes.
Action needed means that the student is at or very close to the due date.
According
to the official rules, once set to action needed, the student has 3 days to
complete
the task or we reopen it for other students.
Certainly not a perfect system though. This is why we like to primarily keep
track
of the status on the d.o issue queue. We just use the statuses here to indicate
whether the student is making progress on the task or not.
Thanks for your quick review on this one!
Original comment by acli...@gmail.com
on 8 Jan 2008 at 1:23
Updated submission. Details on changes are available at
http://drupal.org/node/207196.
Original comment by j.boomba...@gmail.com
on 8 Jan 2008 at 9:09
Attachments:
Original comment by chx1...@gmail.com
on 9 Jan 2008 at 5:35
Original comment by acli...@gmail.com
on 21 Jan 2008 at 4:05
Original issue reported on code.google.com by
chx1...@gmail.com
on 7 Jan 2008 at 8:34