I’ve done exactly that, had multiple fast switch users on a single cpu with Ep connecting to each in turn. Handy to avoid dealing with some environmental issues. That’s where the advice for no passwords and careful notes comes in. Treat each fast switch/sut as an independent platform.
Keep in mind that eggplant can only be connected to one SUT at a time, but you can hand off control during an extended process to another sut, timing needs to be observed. For example, if you start a file save process that is lengthly, as soon as the progress dialog appears you can switch off to a second sut and begin a new routine…
Of course if you have the correct license you can run multiple command line interfaces and test concurrently
Again, if you are off the main network you can forgo passwords, makes the setup much easier in the beginning. May want to hone your skills on calls and lists so you can inject a login routine to your script after you get it dialed in and running smoothly. You really do want to use passwords all around to protect system integrity, but you don’t want security getting in the way of the initial results you surely crave.
After the concept is proven, tighten things up.
With a little study you can create a password routine that calls data from a file for each sut and enters the appropriate password for each.
Have fun…testing can be tedious work at times, so keeping it simple applies more then ever during the early days. Plenty of time for polish later on…and oh yes…comment, comment comment in your code that helps when you want to keep the process clear like water…and cool like ice…