Book Image

VMware ThinApp 4.7 Essentials

By : Peter Bjork
Book Image

VMware ThinApp 4.7 Essentials

By: Peter Bjork

Overview of this book

VMware ThinApp 4.7 is an application virtualization and portable application creator which allows users to package conventional applications so that they are portable. "VMware ThinApp 4.7 Essentials" shows you how to deploy ThinApp packages in order to improve the portability, manageability and compatibility of applications by encapsulating them from the underlying operating system on which they are executed. Application virtualization improves the portability, manageability and compatibility of applications by encapsulating them from the underlying operating system on which they are executed. VMware ThinApp 4.7 is an application virtualization and portable application creator which allows users to package conventional applications so that they are portable. ThinApp eliminates application conflicts, reducing the need and cost of recoding and regression testing. In this book you will learn about how application virtualization works and how to deploy ThinApp packages. You will learn how to update and tweak ThinApp Projects before distribution. This book will then cover design and implementation considerations for future ThinApp projects.
Table of Contents (15 chapters)
VMware ThinApp 4.7 Essentials
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

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...