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 9: | Line 9: | ||
== How to == | == How to == | ||
− | + | [[Media:JUnit_for_PHPIDE.ppt]] | |
== Unit Test Reports == | == Unit Test Reports == | ||
* Last unit testing report here... | * Last unit testing report here... |
Revision as of 09:48, 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".
How to
Unit Test Reports
- Last unit testing report here...