New answers tagged regression-testing
One possibility: Run each thread against its own instance of the application. Depending on the cost of instances, this may be too expensive. But it does eliminate crosstalk among tests.
Whenever I am writing automation around "New" logins, you really have to ask yourself: "Is this new user necessary?" a lot of times in my earlier years I would create a new user each time I did a test, and realized I only needed to create a few to handle all of my testing steps. This may not be the prettiest answer, but following best practices will minimize ...
The first thing I would start with is ensuring that you aren't testing more than one type of user repeatedly. Check out "equivalence partitioning".
Top 50 recent answers are included