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) (→Mailing List and RSS) |
||
| Line 16: | Line 16: | ||
== Mailing List and RSS == | == Mailing List and RSS == | ||
| − | In order to be updated on test issues, register | + | In order to be updated on test issues, register pdt-unit-test@eclipse.org at |
| − | [https://dev.eclipse.org/mailman/listinfo/ | + | [https://dev.eclipse.org/mailman/listinfo/pdt-unit-test https://dev.eclipse.org/mailman/listinfo/pdt-unit-test] |
<br> | <br> | ||
| − | also an RSS feed can show you bug status: [http://download.eclipse.org/tools/ | + | also an RSS feed can show you bug status: [http://download.eclipse.org/tools/pdt/downloads/rss/center.xml http://download.eclipse.org/tools/pdt/downloads/rss/center.xml] |
== Unit Test Reports == | == Unit Test Reports == | ||
Revision as of 05:11, 9 March 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
Mailing List and RSS
In order to be updated on test issues, register pdt-unit-test@eclipse.org at
https://dev.eclipse.org/mailman/listinfo/pdt-unit-test
also an RSS feed can show you bug status: http://download.eclipse.org/tools/pdt/downloads/rss/center.xml
Unit Test Reports
Nightyly build reports include unit test results.
Access to unit test results:
http://download.eclipse.org/tools/php/downloads/drops/N<date>/results/TEST-php.html