
Scenario 1 - Serial Testing:
In the example below, you might have only a single QA engineer to perform tests on your software across various versions of windows, languages or browsers. The reason you may only have one QA engineer may be due to the fact that they are the product specialist and innately know the product inside out, or it may be due to budget restriction.
Each test is performed by the QA engineer in serial, that is, after testing on one platform, they will move onto the next.
In the next example, we have 6 QA engineers, each testing a platform, browser or language.
In the final example, we have 1 QA engineer, using the Shadow™ QA System. This engineer can test and control multiple systems simultaneously. Their product expertise is leveraged, and their productivity is multiplied.
As you can see Shadow™ can control several machines at the same time. In a typical setup a user might have as few as 1 or as many as 5 or more machines configured to be viewed from one single location. Each keyboard and mouse for a machine can be controlled at the same time, each following the actions taken on a particular machine. Alternatively the user can interact with each individual machine separately.