-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Unit tests - prove stability of Drupal Toolkit #529
Comments
JIRA Comment by user: rcook Comment body: Create extensive unit tests (automated tests). This will be very useful in every later development of Drupal Toolkit. This is the set of test that need to exist and added to that can be run to prove that future coding doesn't break anything. Let’s start with a list of tests, write a few, review them, and then proceed. Peter to break this out into smaller tasks. |
JIRA Comment by user: rcook Comment body: Peter, moving to the "Stability" milestone. I think it would be good to see what could be done in this area. |
JIRA Comment by user: rcook Comment body: Can you create a list of the most critical unit tests that you would like to include. We are not going to have time to do everything before you leave, so at this point , perhaps just write down the unit tests you think of as important, and then pull out the most critical for this work and we can add the rest to a new issue for a future set of work. |
JIRA Comment by user: rcook Comment body: I will move this, but I am still interested in hearing thoughts on how we can develop and do release management in DT such that we minimize "breakages" by the execution of some Unit Tests prior to each release. [~mwesley] and [~admin] |
JIRA issue created by: rcook
Originally opened: 2010-10-28 03:06 PM
Issue body:
(nt)
The text was updated successfully, but these errors were encountered: