It would be nice to have a pool of legitimate users with unique passwords that Jenkins could draw on in a quasi-random fashion for test runs.
This would prevent issues like edit conflicts as well as ensuring other sorts of increased test isolation.
Dan and Chris invented this idea while hacking on the Echo tests that rely on multiple users.
I am not sure how useful this would be. I think we should focus on running tests in isolated environments, where users could be created as needed.
It is time to promote Wikimedia-Hackathon-2015 activities in the program (training sessions and meetings) and main wiki page (hacking projects and other ongoing activities). Follow the instructions, please. If you have questions, about this message, ask here.
I don't see a good use case for now. If we ended up needing such thing later on we can fill a new task with a detailed requirement.