Closed (fixed)
Project:
Project
Version:
6.x-1.x-dev
Component:
Tests
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
18 Apr 2010 at 18:25 UTC
Updated:
4 May 2010 at 23:30 UTC
Jump to comment: Most recent file
Here's a start, I plan to move the createProject method to a separate class and have all the test* methods live in classes that extend ProjectTestCase.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | 774706-project-tests-11.patch | 1.9 KB | mikey_p |
| #8 | 774706-8.project_test.patch | 4.63 KB | dww |
| #7 | project_tests-7.patch | 4.4 KB | mikey_p |
| #4 | project_tests-4.patch | 4.82 KB | mikey_p |
| #2 | project_tests-1.patch | 432 bytes | mikey_p |
Comments
Comment #1
dwwA few related efforts:
#279515-29: setting an installation profile for a test doesn't run hook_install_tasks()
There's also a bunch of Project*-related setup code in some tests for PIFT:
http://drupalcode.org/viewvc/drupal/contributions/modules/project_issue_...
http://drupalcode.org/viewvc/drupal/contributions/modules/project_issue_...
Comment #2
mikey_p commentedHere's a follow up to move the abstracted stuff such as createProject to ProjectWebTestCase, so that ProjectTestCase and ProjectIssueTestCase can extend a common class where we can stash basic functionality (like createProject).
Comment #3
dww@mikey_p: wrong patch. ;)
Comment #4
mikey_p commentedYes :(
Comment #5
dwwgreat start, thanks! a few questions:
A) WTF?
Why not just:
?
B) What's up with the patch against project.js? ;)
Thanks!
-Derek
Comment #6
dave reidD6 simpletest's setUp() doesn't accept only one parameter for an array of modules, that's why cufa() is needed since it needs to pass each module name as a separate parameter.
Comment #7
mikey_p commentedSorry about the mixup with project.js (it's not *that* wrong). Part of my notes from #371957: Add customized per project type related vocabularies were included.
This is passing for me.
Comment #8
dwwRan locally myself and saw all assertions pass, yay! Fixed some comments (see attached patch), and committed to HEAD.
YAY!!!
Comment #9
grendzy commentedmore tests at #775052: Automated tests for project_release module
Comment #10
dwwFor posterity. ;)
Comment #11
mikey_p commentedIt'd be good to have a standard pattern for this, updating project.test to match #776128: Add tests for issue creation (including metadata fields).
Comment #12
dwwYup, totally agreed. Ran tests locally and got all passes. Code looks good. Not going to wait for the bot -- committed to HEAD. Thanks!