Index: xdocs/subcomponents/stresstest/index.xml =================================================================== --- xdocs/subcomponents/stresstest/index.xml (revision 0) +++ xdocs/subcomponents/stresstest/index.xml (revision 0) @@ -0,0 +1,140 @@ + + + + + + + + Stress test framework + Harmony Documentation Team + + + + +
+

+

+

+
+ +
+

+

+

+
+ +
+

+ The simplest example of comparative apporach is the following. +

+
+ Tester: My test fails on Harmony VM and passes on RI. Please, + fix Harmony VM. +
+

+ This usually does not work for stress tests. +

+
+ Developer: Who told you that OutOfMemoryError should be thrown + in your thread? My finalizer thread is just a normal java thread, like + yours, and it can fail as well. You have a bug in your test. +
+

+ + There are multiple reasons why we always will have such bugs in the + tests. +

+ + +

+ How can we have a maintainable test product takung all this limitation + into account? We need to learn how to live with occasional failures of + the stress tests. This means, instead of fail, the test should better + report how good it is on Harmony VM compared to RI: +

+ + +

+Developers are better convinsed to fix "the worst issue" or "dergadation" instead of "some issue". +

+

+ +Several metrics for each test: +

+

+ +
+ + + +
Index: xdocs/documentation/documentation.xml =================================================================== --- xdocs/documentation/documentation.xml (revision 410075) +++ xdocs/documentation/documentation.xml (working copy) @@ -49,6 +49,9 @@
  • Documentation for Harmony's Regular Expression Framework
  • +
  • + Documentation for the Stress Test Framework +