Announcing TestNG 5.1: making testing easier, one thread at a time « Otaku, Cedric's blog
In this example, the two test methods testf1() and testf2()
test the methods A#f1 and A#f2 respectively, but when you ask
TestNG to run these tests in parallel mode, these two methods will be invoked
from different threads, and if they don't properly synchronize with each other,
you will most likely end up in a corrupt state.
One way to solve this problem is to declare that the test methods depend on
each other, thus forcing TestNG to run them in the same thread, but that's
obviously tedious and also not semantically correct (they don't really depend on
each other).
Another possibility is to make A#f1 and A#f2 properly
synchronized, but again, it's a lot of work just to enable testing, and while
I'm fine with making minor modifications to my classes to make them easier to
test (making certain methods more visible, adding accessors, etc…), I think
that making my classes multithread-safe crosses the line.
Therefore, TestNG 5.1 provides a new attribute in the @Test
annotation, which can be specified at the class level:
Read full article from Announcing TestNG 5.1: making testing easier, one thread at a time « Otaku, Cedric's blog
No comments:
Post a Comment