It seems that when TestNG runs in parrallel="methods", all methods in
a class share the same class variables. In other word, testNG does
instantiate the test object only once and invokes methods of that
object concurrently.
For me, it seems bad since multiple methods could modify the class
variables and stumbles on other thread.
Can anybody clarify that my understanding is correct"
--haison
On May 11, 2:50 pm, "Cédric Beust ♔ " <cbe...@google.com> wrote:
> Your understanding is correct. How about using a ThreadLocal to save
> per-thread data?
>
> --
> Cedric
>
This is not an issue. TestNG advocated right from the beginning that
state testing is important. Moreover, TestNG is not just an unit
testing framework (where argueable the instance per test method fits)
and so TestNG has gone this different path.
./alex
--
.w( the_mindstorm )p.
TestNG co-founder
EclipseTestNG Creator
Thanks again,
Gili
--
You received this message because you are subscribed to a topic in the Google Groups "testng-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/testng-users/oWxn6YocEAQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to testng-users...@googlegroups.com.
To post to this group, send email to testng...@googlegroups.com.
Visit this group at http://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/d/optout.