Vladimir Ivanov wrote:
The more I work with our tests the more I see that managing tests via
directory layout is worse than using metadata.
Agree :-)
I thought about three more characteristics we might want to mark-up tests
with:
- Platform-specific unit tests
- Harmony implementation test vs. API tests
- Broken buggy tests
- Tests failing due to bug in implementation
- [Potentially in future] type of test - unit, functional, stress,
reliability, etc.
- [Potentially in future] regression test
- Each of the listed above can be:
- OS-specific
- Processor architecture-specific
NEW – Test should be executed only in separate JVM
NEW – Long running test
NEW – Non-re-enterable test
We already have "only in separate VM" tests, for example
org/apache/harmony/logging/tests/java/util/logging/LogManagerTest.java
*Long running– we might want to mark-up such tests sometime later when we
have long-running tests and do not want to execute them in quick
pre-integration testing for example.
*Non-re-enterable – we might want to mark-up such tests when we try to
re-use unit tests in unusual modes – for example for reliability or
stress
testing purposes.
Wow, so sophisticated! But would you please integrate this with George's
proposal[1], so that we could have a common discussion base? Thanks a lot.
[1]http://www.mail-archive.com/harmony-dev@incubator.apache.org/msg10229.html
Best regards,
Richard
thanks, Vladimir
--
Richard Liang
China Software Development Lab, IBM
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
