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) |
|||
| Line 16: | Line 16: | ||
== Unit Test Reports == | == Unit Test Reports == | ||
| − | + | Nightyly build reports include unit test results, the reports are locted under | |
| + | /tools/php/downloads/reports/ folder, if you want to access one of the reports use: <br> <br> | ||
| + | http://download.eclipse.org/tools/php/downloads/reports/TEST-php''<Date>''.html <br> | ||
| + | |||
| + | for example [http://download.eclipse.org/tools/php/downloads/reports/TEST-php20070107.html] | ||
Revision as of 16:57, 7 January 2007
Background
"Testing: Early, Often and Automated" (Extreme Programmin Explained by KENT BECK)
The PDT team has accepted the XP ([1]) two principles to increase the cost-effectiveness of testing: double checking and the Defect Cost Increase.
We release the "PDT test framework" that helps us write unit tests for PDT in a very fast way.
"The sooner you find a defect, the cheaper it is to fix".
Resources
- PDT Test Framework Tutorial - [2]
Unit Test Reports
Nightyly build reports include unit test results, the reports are locted under
/tools/php/downloads/reports/ folder, if you want to access one of the reports use:
http://download.eclipse.org/tools/php/downloads/reports/TEST-php<Date>.html