You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I browsed the parallel execution framework. I have done work in past
related to this and know how to reliably speed up this framework with:
(a) less locking
(b) far less self-imposed sleeps/waits
However, I do not see any unit tests.. Without unit tests there is no
mechanism to prove the changes.
I don't expect Load and Performance tests (though would be nice..) in any case
I can write those. But need FUNCTION/FEATURE unit tests to prove the features
working same under the (much higher) load conditions that my new code would
support.
Why think that no tests?
(a) the tests dir is EMPTY
(b) Even under src: I searched for AbstractSimpleParallelTask: and only found
it in source code (no testcases..)
Let me know: How did/do you regression test this project ? And then .. how did
you verify your AbstractSimpleParallelTask is working in the first place?
thanks
Original issue reported on code.google.com by [email protected] on 29 May 2011 at 10:14
The text was updated successfully, but these errors were encountered:
Thanks for the interest in the project.
Unfortunately, as you pointed out there are no unit tests at the moment. The
only functional tests are done via many BeanShell in scripts/ directory.
On how do I ensure that AbstractSimpleParallelTask (or related) is working in
the first place is by using them in actual application code as in the case of
http://code.google.com/p/metastudio/source/browse/trunk/metastudio/src/org/meta/
math/qm/property/OneElectronProperty.java or
http://code.google.com/p/metastudio/source/browse/trunk/metastudio/src/org/meta/
math/qm/TwoElectronIntegrals.java
In view of your interest, I will be adding you to the project. Hope this is
fine with you :)
Original issue reported on code.google.com by
[email protected]
on 29 May 2011 at 10:14The text was updated successfully, but these errors were encountered: