Effective test procedures
It’s all about your test procedures. The first test procedure I’ll explain targets minimizing the number of variables you’re facing, helping you to focus on what is most likely the cause of the issue. The VMware ThinApp blog (https://blogs.vmware.com/thinapp/2010/10/thinapp-troubleshooting-methods.html) discusses the test procedure, consisting of four steps, for minimizing the variables. The four steps should be conducted in a sequence. If one test step fails, there’s no point conducting a new test step because the next one will fail as well. Stop at the failing test step and try to solve why the package is failing before moving on.
The test procedure should be used when there’s an issue with a package. You’re not supposed to run through all the four steps with all your packages.
Let’s have a closer look at each step.
The Dirty Test
The Dirty Test means that when you have just finished the capture process, while the captured application is still locally installed on...