Sharing Automation envs along with Manual Testing
I am trying to guage how many QA Environments(web servers)people have at their respective companies. We currently have 4. One for automation, two for manual testers and one for integration testing. Management (in their infinite wisdom) wants to combine our automation env (WinRunner) along with the manual testing envs. Can anyone provide reasoning why this is bad idea? Also, if you could provide how your testing environments are setup, I would very much appreciate it.
Re: Sharing Automation envs along with Manual Testing
I currently have no choice but to share the same client/server setup which we use for manual testing as well as automated. My way of handling this to date is:
1. Dedicated test automation client PCs (with Winrunner installed).
2. Dedicated user accounts on the servers to be used only for automated testing.
3. The automated tests are designed with the fact in mind that I cannot count on pre-existing test data to be untainted by the manual testers, nor can I simply reset the database to a known baseline (it would impact the manual testers, and besides it is a very large database distributed across many servers). Thus each test needs to create its own test data at run time (and clean up after itself when necessary).
[i]...Sound trumpets! Every trumpet in the host! / Sixty thousand, on these words, sound, so high the mountains sound, and the valleys resound.</i] (The Song of Roland)