Before we begin creating a test, we need to analyze our application and determine our testing needs.
First, determine the development environments in which our application controls were developed, such as Web, Java, or .NET, so that we can load the required QuickTest add-ins.
Then determine the functionality that we want to test. To do this, consider the various activities that customers perform in our application to accomplish specific tasks. Which objects and operations are relevant for the set of business processes that need to be tested? Which operations require customized keywords to provide additional functionality?
While we are thinking about the business processes we want to test, consider how we can divide these processes into smaller units, which will be represented by our test's actions. Each action should emulate an activity that a customer might perform when using your application.
As we plan, try to keep the amount of steps we plan to include in each action to a minimum. Creating small, modular actions helps make our tests easier to read, follow, and maintain.
