Task flow for testing applications

You can find the task flow for testing the application using IBM® DevOps Test UI (Test UI).

Although the task flow implies that each task is completed sequentially, you can do many of the tasks at the same time.

The task flow for functional testing using Test UI is as follows.


S/N	Tasks	More information
1	Verify the domains and controls that are supported for functional testing.	Test application domain support.
2	Optionally, use the proxy SDK to develop proxies that enable support for controls.	DevOps Test UI proxy SDK.
3	Set up functional test environment.
3.1	Set preferences.	Setting preferences.
3.2	Enable environments.	Preparing the functional test environment.
3.3	Configure applications.	Configuring applications for testing.
4	Create a functional test project.	Creating a test project.
5	Create a functional test scripts.	Simplified scripting	Java or Visual Basic scripting
5.1	Record a script or insert a manual script.	Creating a simplified test script.	Recording a Java test script.
5.2	Insert verification points.	Inserting verification points into the script using the application visuals.	Verification points.
5.3	Insert data-driven commands.	Inserting data-driven commands into a script by using an application visual	Data-driving functional tests.
5.4	Insert additional controls for testing.	Inserting an application control into the script by using an application visual.	Adding test objects to a script.
5.5	Optionally, switch to Java scripting.	Switching to Java scripting.	NA
6	Play back scripts.	Running scripts from DevOps Test UI.
7	View logs.	Viewing logs in the Projects view.

Note: Test UI automatically enables the environments for functional testing. As a result, you can directly record functional test scripts without enabling components manually. The automatic enablement takes place under certain conditions and has limitations. For more information about the conditions and limitations, see Automatically enabled environment for functional testing.

Basic tester: A basic tester can record functional test scripts that are generated as simplified test scripts. The tester does not require programming knowledge to edit the functional test scripts. The tester can switch to Java scripting, and use the Insert Java Code Snippet or Insert Java Method features that are available in the simplified script editor. The tester then starts to work with the Java test script directly. You can use the application visuals to insert verification points, data-driven commands, and additional controls for testing.

Advanced tester with scripting knowledge: A tester with Java or Visual Basic programming knowledge can either record functional test scripts or create the test scripts manually. You can use the test object maps to update the objects and insert additional objects for testing.

Developers: A developer who knows theTest UI framework and programming based on the proxy framework can write proxies for adding support to test the controls that are not supported by default for functional testing.