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) (→Unit Test Reports) |
Roy.zend.com (Talk | contribs) (→Unit Test Reports) |
||
Line 16: | Line 16: | ||
== Unit Test Reports == | == Unit Test Reports == | ||
− | * | + | * [Bare Junit Report] (first draft) |
Revision as of 04:50, 6 December 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.
"The sooner you find a defect, the cheaper it is to fix".
Resources
- PHPIDE Test Framework Tutorial - [2]
Unit Test Reports
- [Bare Junit Report] (first draft)