test Automation shall work for us unattendedly, preferably when we are not at the office. It requires Access to our application System and it requires the ui to be left unlocked. This imposes security risks.
What are You doing against it? Which measures do You take?
Hi,
Our testing environment is fully isolated inside virtual "ecosystem", which is the exact copy of our production system.
We are also working on a duplicate of the production system that is behind firewalls. Also, most of our overnight tests are running on virtual machines that are only accessible by specific login. The UI, etc. are unlocked on that VM. Even if a test is left running on a laptop, that laptop is locked.
we also have separate environment that are isolated.
also have sanitized data bases.. where with some database scripts we jumble/replace sensitive data.
fo eg customer name looks like Pxxxr Pyn which was Peter Pan in real database
