Summary

This article answers the question: "What do I need to do so that my testers can start their application testing work?" This article provides a blueprint of the overall steps to configure the testing environment up to the point where testers can perform application testing. At the end of these steps, you have:

• A TMF system that can talk to a target test system and the application on that system
• Team members (operators) that can define and run tests for the target testing application
• A starter set of scenarios for them to start using to set up test suites and run tests

After you complete the actions outlined in this article, your team members will be able to log into TMF and start testing an application using the features of TMF.

Assumptions

This article gives an overall view of the key steps that need to be done and the elements that need to be in place so that a testing team can begin performing their work of testing applications and managing that testing using TMF. Each main step in this overall blueprint links to PDN articles that provide finer details, so that you can drill down as needed.

This article assumes:

• TMF itself is successfully installed on a system
• The essential TMF connectivity pieces are successfully installed on a system running Version 6.1.1
• An application that the testing team intends to test exists on the target test system
• That application was created using the Direct Capture of Objectives (DCO) methodology (using the Application Profiler and the Application Accelerator), or was enabled to use DCO

Overview

1. Ensure that TMF is installed successfully.
2. Create a "testing" application.
3. Configure the TMF elements in a target system and testing application.
4. Add that target test system as a TMF environment.
5. Add that testing application to the environment record.
6. Associate TMF users with that testing environment.
7. Create a starter set of scenarios by running the Scenario Builder.
8. Complete a scenario.

Step 1: Ensure that TMF is installed successfully.

The system that has the applications you want to test is usually called the "target test system" or the "target system". For TMF to work as designed, the target test system should be a different system than the one where TMF itself is installed. Part of the TMF installation process includes installing some elements into the target system.

Step 2: Create a "testing" application.

This is a best practice step. For each application in the target system that you are developing and want to test using TMF, it is a good practice to create a "testing application" that is built on the one you are developing.

Step 3: Configure the TMF elements in a target system and testing application.

In the target system, some configuration steps must be completed so that TMF can communicate with the target system and testers can run automated unit tests in the testing application.

Note: If you created a testing application in Step 2, make sure you add the PegaCESvcs RuleSet to the Component and Shared RuleSets array of that application's rule form, as part of this step.

Step 4: Add that target test system as a TMF environment.

In TMF, environment records are used to make test systems and testing applications known to TMF. TMF organizes and manages the testing work by associating testers with the testing applications through the environment records.

Step 5: Add that testing application to the environment record.

Before you can save the environment record, add at least one application to be tested to it.

To complete this step:	In the Environment Details section from Step 4, click and add the testing application. After adding the testing application, save the environment record. (See Manage testing environments).
What success looks like:	The target system is listed in the Maintain Environment Data section.

Step 6: Associate TMF users with that testing environment.

Before TMF users can perform assigned tasks testing an application, the users need to be associated with the testing environment record created for that application. Logged into TMF as TestManager, associate the application from Step 5 first with the TestManager user and then with the Tester1 user.

To complete this step:	a. Logged in as TestManager, click Test Manager > Preferences. In the User Preferences window, use the button to add the testing environment to your environments list. (See Maintain Resources). Select a default one also and save. b. In the portal, click Maintain > Resources. Find the Tester1 user and Update. Add an environment and select a default one and save the choices for Tester1.
What success looks like:	Log out of TMF and log back in as either TestManager or Tester1. Instead of the welcome message from Step 1, the test portal displays and the in-context application is the selected default. (See About the test portal.)

Step 7: Create a starter set of scenarios by running the Scenario Builder.

The first element required for testing an application is a test scenario. Use the Scenario Builder guided wizard to create a starter set of scenarios for the application to be tested.

Step 8: Complete a scenario.

Complete the definition of one of the scenarios generated by the Scenario Builder.

Next steps

At this point, testers can:

• Execute the scenario
• Create additional scenarios
• Create a test suite of the scenarios
• Run that test suite

Read these TMF articles to become more familiar with the TMF interface and its test management features:

• Configuring the framework
• Using the administrative functions to manage your testing operations
• About the test portal
• Using the Scenario Builder
• Defining scenarios and test suites
• Running tests
• Reporting test progress and results
• Customizing test document templates