Stefano Maestri [
http://community.jboss.org/people/maeste] created the discussion
"Re: TestSuite - multithreaded tests and stress test"
To view the discussion, visit:
http://community.jboss.org/message/573318#573318
--------------------------------------------------------------
I've investigated more deep byteman, and I think it could be useful for some tests
where (as Kev said) deterministic concurrent execution will be needed.
I'm thinking about (for example) to connection pooling state after some particular
situation happened to some thread using connections or statements from that pool. Errors
situation or not clean use of the api by the user.
This kind of advanced tests, verifying robustness of our implementation have to be well
designed to keep them readable and to stress our codebase in a correct way. Moreover we
have to decide also which kind of "not clean" use of our implementation and
user's situations we would monitor and verify by the test suite and which we would
just well document as not correct. Of course even testes ones have to be documented.
That said, I think we need also some simpler way to write multithreaded tests to implement
a stress test suite. In my ideal world we could have a lot (maybe not all) unit tests that
could be launched in a stress tests suite with relatively high concurrence and tracking
execution time (with a report as fine as possible to spot at least at macro level if and
when a component is not scaling well). As already said a declarative (aka annotation)
solution to define test concurrence would be more than nice.
regards
S.
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/573318#573318]
Start a new discussion in IronJacamar Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]