How to set up a clean test machine for each test
I want to know if there are any general guidelines in which programmers in general and QA in particular follow a clean test system setup.
The system needs to be clean every day, without any unnecessary dependencies (like .NET), without the ghosts of previous tests and checks, and fairly easy to simulate and modify.
Any advice would be greatly appreciated!
+2
a source to share
2 answers
It's relatively simple. Either use a virtual machine with snapshot capabilities, download a copy of the virtual machine image, or use a full system rendering (like Ghost). If you want to use a fully patched system, you need to update them every couple of months.
I would refrain from re-creating the given schedule. I ran a test that spanned two or more business days.
0
a source to share