Re: Data driven tests within the distributed Grinder TesterCluster
Juno Yoon <[email protected]>
| Newsgroups | gmane.comp.java.grinder.user |
|---|---|
| Message-ID | <CAMh00CGq1F21z55iDa0RUPHNcjx7WbpwLNe8-jxNfBSXC84xZQ@mail.gmail.com> |
This might help you. http://www.cubrid.org/wiki_ngrinder/entry/how-to-make-each-thread-act-differently This is written in groovy which nGrinder uses However you may be able to port this Python very easily. 2014-04-04 3:07 GMT+09:00 Lawrence Schapker <[email protected]>: > Thank you everyone who replied! > > I created a python class that generates the overall number of threads and > the unique thread number as explained below. This algorithm was what I > expected, but I wanted to verify that someone had not already "invented > that > wheel." > > One thing that I has to do was with the rest call that starts all of the > agents, I had to include the number if agents as a parameter (i.e. > -Dgrinder.agents=X). My "ThreadIdentity" class seems to work well. If > anyone is interested, please let me know. > > Thanks again! > > Larry Schapker > > > > -- > View this message in context: > http://grinder.996249.n3.nabble.com/Re-Data-driven-tests-within-the-distributed-Grinder-TesterCluster-tp8779p8792.html > Sent from the Grinder - User mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > _______________________________________________ > grinder-use mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/grinder-use > ------------------------------------------------------------------------------ _______________________________________________ grinder-use mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/grinder-use