Here’s my situation:
App I’m testing contains several more or less independent components, and one of them is an authentication system.
On one hand, I’d like something like 100 concurrent threads performing some actions on app, imitating logged in users actions, to have a decent load.
On another hand, I’m not allowed to create more than like 50 user sessions on this authentication system.
Number of concurrent user sessions is not really important for what I’m testing. Reusing user sessions will put some limitations, but is ok in general in my case.
It could be even a single user session.
Is there a proper way of doing something like following:
- Login is performed once (it is 1 or 2 http requests depending on situation).
- When token is received, it is saved and accessible to all threads.
- After this, load test workflow itself starts, with all threads using the same login token.
Or it is a totally bad idea?
I’ve got some concerns with this workflow, e.g. how to re-login in case of some errors that break user session (and it can happen in my case) etc. But it could be useful for some specific tasks.
Did anyone do something similar?