--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, 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.
Mrunal
I beg to differ with you on that. It's very much possible and I don't think it's any limitation of Testng for sure.
By restricting the data provider thread count one can ensure that the test instances are created one at a time. By using depends on within a test class which the factory produces ordering of methods can be guaranteed.
So what exactly is this limitation you are talking about ?
Hi SampathIf you are creating test instances using @Factory and @DataProviders then i am sorry it will not run in sequence as you wish, it will run in random order. Courtesy : limitation of TestNG implementation.
--
Hi Krishnan
Mrunal
First and foremost my apologies for not understanding completely what you were trying to say. Yes I understand now what you were hinting at. Let me see if I can deep dive into Testng code base to understand if there are any alternatives.
And oh btw thanks for correcting me and giving me a chance to learn something new. 😆
--
--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/testng-users/738a5a0a-2bda-4e73-a9eb-81225e9560d7%40googlegroups.com.