Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PDT/Testing Framework"
< PDT
Roy.zend.com (Talk | contribs) (→How to) |
Roy.zend.com (Talk | contribs) (→How to) |
||
| Line 7: | Line 7: | ||
Remember: "The sooner you find a defect, the cheaper it is to fix". | Remember: "The sooner you find a defect, the cheaper it is to fix". | ||
| − | == | + | == Resources == |
| − | * | + | * PHPIDE test framework tutorial - [http://wiki.eclipse.org/images/2/20/JUnit_for_PHPIDE.zip] <br> |
| + | |||
| + | * Assigning a new unit test to PHPIDE. <br> | ||
| + | |||
| + | * List of components to unit test. <br> | ||
== Unit Test Reports == | == Unit Test Reports == | ||
* Last unit testing report here... | * Last unit testing report here... | ||
Revision as of 10:21, 22 November 2006
Background
"Testing: Early, Often and Automated" (Extreme Programmin Explained by KENT BECK)
The PHPIDE team has excepted the XP ([1]) two principles to increase the cost-effectiveness of testing: double checking and the Defect Cost Increase.
We release the "PHPIDE test framework" that helps us write unit tests for PHPIDE in a very fast way.
Remember: "The sooner you find a defect, the cheaper it is to fix".
Resources
- PHPIDE test framework tutorial - [2]
- Assigning a new unit test to PHPIDE.
- List of components to unit test.
Unit Test Reports
- Last unit testing report here...