Information in this topic applies to desktop and web applications. |
To check that your application works correctly on different Windows versions, you need to test it on all of them.
Creating tests for different Windows versions may be tricky, because there are some differences between them. For example:
-
Windows system paths and file names: C:\Users vs C:\Documents and Settings, Documents vs My Documents, and so on.
-
Different UI in standard system dialogs (Open File and others).
-
Different settings of User Account Control (UAC), which prevents applications from performing privileged operations unless they have administrator permissions.
TestComplete includes features that make it easier to create tests for different Windows versions:
-
The
Sys.OSInfo
andaqEnvironment
objects let you check the Windows version to include version-specific operations in your tests. -
The
OpenFile
andSaveFile
methods let you work with the Open File and Save File dialogs in the same way on different Windows versions.
For common tasks and solutions, see the topics of the Running Tests on Multiple Operating Systems - Typical Tasks section.
General Approach
The overall procedure of creating tests to be run on multiple operating systems contains the following steps:
-
Plan steps your test will perform and determine which steps will be common for all operating systems and which steps will be specific to particular operating systems.
-
Implement test steps. It is recommended that test steps be implemented as separate script routines, keyword tests, low-level procedures, and so on.
-
Group created steps so that steps specific to operating systems are run only on corresponding operating systems and common steps are run on all operating systems. To manage created steps, you can use test items or you can manage them from other tests. For more information on that, see Running a Test by Name.
-
Select the environment where your tests will be run. You can either use physical computers, or virtual computers with desired operating systems installed. Make sure you have network access to computers where the tests will be run and those computers have TestComplete (or TestExecute) installed.
-
Select an approach you will use to control test runs on other operating systems:
-
You can control the tests manually, that is, you have to log in to computers with the desired operating system running, copy the tests there and initiate a test run.
-
To control the tests, you can use the TestComplete Network Suite feature that allows managing test runs on different computers.
-
Analyzing Results
After you run your tests on several operating systems, you may want to gather results generated for each operating system, compare and analyze them. For each test run TestComplete generates a test log that contains information on all actions performed during the run.
Explore the test log generated for your tested application on different operating systems to learn whether the tests are successful. To view the test log generated for your tested applications on multiple operating systems, you can either log in to the remote computers where the tests were run and access the logs manually or you can use various features provided by TestComplete for managing logs.
For more information on working with TestComplete logs, see Test Results.
Note: | If you use a network suite to control test runs, you can configure it to gather test results automatically. After a test run is finished, all results will be copied from the remote computers to the computer from which you control the test run and included into a common network suite log. |
See Also
Running Tests on Multiple Operating Systems
Creating Tests
Tests, Test Items, and Test Cases
Test Results