Storing Scripts and Test Results

This chapter provides an overview of storing scripts and test results and discusses how to:

• Work with the script repository.

• Work with script reporting.

• Work with JD Edwards Autopilot Test Manager.

• Manage script testing.

Understanding Storing Scripts and Test Results

Scripts that you write are reusable, dynamic objects that continue to be useful after you complete them. Oracle's JD Edwards EnterpriseOne Autopilot enables you to write and run scripts. You can also include those scripts in a base of knowledge about the software and manage batch testing of scripts.

The script repository is a key component of the JD Edwards Autopilot knowledge base. The repository is a database of scripts. It is stable because reposited scripts are controlled copies that can be changed only by the owner or an administrator who has permissions. The database is varied because many people with different areas expertise can contribute to it. Finally, the database is organized because you can assign defining properties to each script that you reposit. These properties enable you to categorize scripts by application, for example.

Capturing and storing test results is another important way in which JD Edwards Autopilot enables you to build a knowledge base about the software. If you configure JD Edwards Autopilot to capture playback results, it generates an event stream during playback. The event stream is a chronological, time-stamped record of JD Edwards Autopilot and JD Edwards EnterpriseOne events that occur during playback. JD Edwards Autopilot stores these test results locally and in a repository, the F97214 table. You can use these results to troubleshoot JD Edwards EnterpriseOne processes. For example, you might identify a processing error or isolate an error message.

The results repository is an important part of the automated testing process. To analyze playback events in detail, you can import an event stream to JD Edwards Virtual Autopilot Script Editor, which is part of JD Edwards Virtual Autopilot. Using JD Edwards Virtual Autopilot Script Editor, you can generate from the event stream a virtual script. You can use the virtual script on a single workstation to simulate multiple users.

Important! JD Edwards Virtual Autopilot requires a JD Edwards EnterpriseOne Windows client. You can use JD Edwards Virtual Autopilot with JD Edwards EnterpriseOne Tools 8.97 and JD Edwards EnterpriseOne Applications 8.10 and prior. You cannot use JD Edwards Virtual Autopilot with JD Edwards EnterpriseOne Applications 8.11 and later releases, as these releases are on a web client only.

JD Edwards Autopilot also enables you to manage the testing of scripts. Using Test Manager, you can create playlists of locally saved and reposited scripts and conduct batch testing. This frees you from the time-consuming task of running one test at a time. You can use Test Manager to conduct testing of an entire suite of applications in one session.

JD Edwards Autopilot Repositories

Scripts that you write are reusable, dynamic objects that continue to be useful after you complete them. JD Edwards Autopilot enables you to write and run scripts. You can also include those scripts in a base of knowledge about the software and manage batch testing of scripts.

The script repository is a key component of the JD Edwards Autopilot knowledge base. The repository is a database of scripts. It is stable because reposited scripts are controlled copies that can be changed only by the owner or an administrator who has permissions. The database is varied because many people with different areas expertise can contribute to it. Finally, the database is organized because you can assign defining properties to each script that you reposit. These properties enable you to categorize scripts by application, for example.

Capturing and storing test results is another important way in which JD Edwards Autopilot enables you to build a knowledge base about the software. If you configure JD Edwards Autopilot to capture playback results, it generates an event stream during playback. The event stream is a chronological, time-stamped record of JD Edwards Autopilot and JD Edwards EnterpriseOne events that occur during playback. JD Edwards Autopilot stores these test results locally and in a repository, the F97214 table. You can use these results to troubleshoot JD Edwards EnterpriseOne processes. For example, you might identify a processing error or isolate an error message.

The results repository is an important part of the automated testing process. You can import an event stream from the repository to JD Edwards Virtual Autopilot Script Editor, which is part of JD Edwards Virtual Autopilot. Using JD Edwards Virtual Autopilot Script Editor, you can generate from the event stream a virtual script. You can use the virtual script on a single workstation to simulate multiple users.

JD Edwards Autopilot also enables you to manage the testing of scripts. Using Test Manager, you can create playlists of locally saved and reposited scripts and conduct batch testing. This frees you from the time-consuming task of running one test at a time. You can use Test Manager to conduct testing of an entire suite of applications in one session.

Script Repository

The script repository is similar to a library. It is a centralized location where you can find and retrieve scripts. You can search for scripts in the repository by browsing through all of the scripts that are available or by focusing your search on, for example, scripts that test a particular suite of applications.

In addition, like a library, the script repository acquires new materials. Each time that you create a script, you can assign distinguishing properties to it and then add it to the repository, from which it can be retrieved and viewed by others. Scripts can circulate freely among those who have access to the system, or you can assign levels of security to scripts to restrict their use.

Unlike a library, you can modify the materials that you remove from the repository. For example, you might check out a script from the repository to modify it. The JD Edwards Autopilot script repository enables a dynamic interchange between the people who use it.

You can use the script repository to build a database of scripts. You use JD Edwards Autopilot to:

• Categorize scripts according to a set of user defined criteria.

• Identify scripts with unique names.

• Add scripts to the repository.

• Browse for scripts.

• Check scripts in or out of the repository.

• Retrieve copies of scripts.

• Modify scripts.

• Assign security to scripts.

• Track changes that you make to scripts.

• Identify scripts that are included in other scripts.

See Also

JD Edwards EnterpriseOne Tools 8.97 Virtual AutoPilot Guide

Script Categorization

Like a librarian who adds books to a library collection, when you add a script to the repository, you assign it properties, such as title, description, the application that the script tests, the purpose of the test, and so on. The properties pages that are attached to each repository script provide important summary information for users who check out a script, and they provide a way for you to categorize scripts and make them easier to find.

Categorizing scripts also facilitates running batch test scripts using Test Manager. Using Test Manager, you can browse the repository for scripts in a particular category, add them to a playlist, and automatically play them back.

Access the Script Properties form by selecting Properties from the File menu. The Script Properties form contains controls with scroll buttons.

The combo boxes contain user defined values. You select from these values to categorize a script. To ensure that the information in the database is consistent, reliable, and easy to access by browsing, use a consistent set of user defined values, which you maintain in table F0004 and table F0005, rather than using individual user text entries.

You can add to the values that appear in the combo boxes by using the User Defined Codes program (P0004A). This table lists the relevant user defined codes (UDCs) that JD Edwards Autopilot uses to populate the combo boxes in the Script Properties form:

Note. The user defined combo box values also appear in the Select Script form and the Add Script to Repository form.

Property Pages for Scripts

As you add a script to the repository, you should complete property pages that provide fundamental information about it, such as title, description, owner, the application that the script tests, and so on. Completing property pages also enables you to classify a script as part of a large-scale testing effort. For example, you can designate these script properties to include the script in a suite of scripts:

• System code.

• Department.

• General use, such as benchmarking.

• Detailed use, such as batch applications.

You document the properties of a script by entering information in the Script Properties form. When you save the script, JD Edwards Autopilot saves the information along with the script.

When you add the script to the repository, JD Edwards Autopilot saves the property page data in the database. This data loads when you check out a script from the repository, and it overwrites any property page changes that you might have made in the local script.

General Tab

The General tab of the Script Properties form contains a series of fields in which you enter data that defines the script.

The information that you enter on this tab provides baseline information about the script and its origins. You enter data in these fields on the General tab of the Script Properties form:

Note. After you add the script to the repository, retrieve it from the repository, and view its properties, fields on the General tab display the reposit date and the last person to open the script, as well as the time and date that the script was opened.

Details Tab

On the Details tab, you can enter information that defines how the script fits into a test management scheme, as well as validation information and information about resetting data.

These fields enable you to enter quality-assurance-related data that is useful in large-scale testing:

• Test Script.

  You enter the collection of related scripts in which yours belongs, such as Tools Applications.

• Test Case.

  You enter the specific function that you are testing, such as activating the Address by Effective Date feature. The values for this parameter are user defined.

Select one of these options to indicate whether script validation occurs automatically or if you need to review the script output manually to determine if it ran successfully:

• Automatic

• Manual

Select the automatic validation option if simply running the script successfully means that the functions worked, and you do not need to further test the results. However, in some cases, such as when you test universal batch engines (UBEs), you must manually review the output of the script to determine whether it was successful. For example, you might need to verify that a UBE report generated successfully.

If you select the Manual option, JD Edwards Autopilot enables these additional options:

• Report

• Screen Prints

• Log Comments

Selecting one or more of these options reminds people who run the script to manually review the output after the script runs.

In addition, you can indicate whether the script resets changes that you made to constants or to master file data, such as additions to or deletions from the F4101 table.

Comments Tab

On the Comments tab, you can enter additional descriptive information about the test, the purpose of the script, and any other information that is relevant.

Categories Tab

The Categories tab enables you to categorize the object of that you are testing. A system administrator creates user defined testing categories, which appear in the form as options. For example, you might define a category of testing as package verification. Options on the Categories tabs–such as Daily Build or Weekly Package–can indicate the type of verification testing that the script performs.

Naming Conventions for Saved Scripts

No predetermined rules exist for naming scripts that you add to the repository. Use a particular naming convention for all scripts. For example, you might give the script a title that identifies the application, release, or function that it tests. In addition, you might specify whether the test is new or a retest. Following a naming convention enables other users to identify the purpose of a script. Assigning properties to the script enables you to accurately subcategorize it; adhering to a naming convention furthers that goal.

See Also

Understanding Script Retention

Add to Repository Command

After you create a script, establish its properties, give it a unique title, and save it locally, you can add it to the repository using the Add Script to Repository form. You can use this form to change the properties of the script before you add it to the repository. However, you cannot specify the owner because JD Edwards Autopilot automatically assigns the owner ID, closes the script to prevent further changes, and adds it to the repository.

Browse Repository Scripts Command

The Browse Repository Scripts command enables you to search for scripts in the repository. You can make the search as narrow or as broad as necessary. After you have found the script that you need, you can create a copy of it or check it out of the repository.

You use these two forms with the Browse Repository Scripts command:

• Select Script

• Browse Scripts

You use the Select Script form to establish search criteria. The Browse Scripts form contains information about the scripts in the repository that have properties that match the criteria specified in the Select Script form.

Select Script Form

The Select Script form contains the same tabs and fields as the Script Properties form. However, it is a query form rather than a form for entering script properties.

You can select any of the tabs, except Comments, and enter data in the fields or select options to establish search criteria for a particular type of script. Alternatively, you can enter the exact title of a script. JD Edwards Autopilot matches the criteria that you set and the entries in the Script Properties pages. If you do not enter any field information, JD Edwards Autopilot includes all scripts in the repository.

All of the fields on the General and Details tabs on the Select Script form–with the exception of the Reference Number field–enable you to use wildcards (asterisks) to have JD Edwards Autopilot include all scripts in the search.

You can use the asterisks alone or with an entry in a field. For example, to find all scripts that tested the 8.11 release, you might enter *811* in the Title field. JD Edwards Autopilot includes in its search all scripts that contain 811 in the title, regardless of any text that comes before or after 811.

If you enter information in a field, JD Edwards Autopilot automatically appends the wildcard to the text string. For example, if you enter P0911 in the Main Application field, JD Edwards Autopilot returns all scripts with a main application property that includes P0911, such as P0911A, P0911B, and so on.

The Reference Number field contains a 0, which indicates that you have not entered a SAR number. If you leave the 0 in this field, JD Edwards Autopilot does not use a reference number as a search criterion and includes all reference numbers, such as SARs, in its search.

If you enter a reference number, you limit your search to those scripts that tested a particular SAR or to tests that are defined by another reference number.

Browse Scripts Form

When you click OK on the Select Script form, the Browse Scripts form appears. This form contains summaries of all scripts that match the data specified in the Select Script form. The Browse Scripts form contains these column headings, which identify a script:

• Title

• Description

• Owner

• User

• Machine

• Security

The script owner is the person designated in the Script Properties form. The user is the last person who checked out or checked in the script. The Machine field identifies the workstation that the user used to check out the script. The Security field indicates the level of security that the owner attached to the script. The security levels and their meanings are as follows:

The form also contains these buttons:

• Get Copy, which enables you to create a copy of a script.

• Checkout, which enables you to check out a script from the repository.

• Undo Checkout, which enables you to undo a script checkout.

• Delete, which enables you to delete a script from the repository if you are authorized to do so.

• Close, which enables you to exit from the Browse Scripts form.

JD Edwards Autopilot disables the Get Copy and Checkout buttons until you select the title of a script. After you select a title, these two buttons are enabled.

You can use the Repository Script Properties form to review the properties of any script that you want to check out by right-clicking any script and selecting Properties. This form contains the four tabs that appear on the Select Properties and Script Properties forms. You cannot change script properties using the Repository Script Properties form.

You can create a copy of or check out a single script. You can also create multiple copies or check out more than one script. You can open the checked-out copy, check it in, or close the form. If you close the form, the script remains checked out. If you select a combination of scripts that you checked out and scripts that someone else checked out, you cannot open a script or check it in.

Deletion of Scripts

You can delete from the repository any script that you own. However, these restrictions exist:

• You cannot delete a script that you do not own unless you have authorization.

• You must enter a password that changes daily to delete a script that you did not add but that you are authorized to delete.

• You cannot delete a script that is included in another script.

Get Copy Command

While you are in the Browse Scripts form, you can create a copy of a script that resides in the repository. JD Edwards Autopilot enables you to view and run a copy of a script that you obtain from the repository, but you cannot make any permanent changes to it without first saving it as a local copy in your script directory.

JD Edwards Autopilot enables the Get Copy button in the Browse Scripts form when you select a script that is not checked out. If you select a checked-out script, the Get Copy command is not available. Instead, you can use the Open command to access a copy of the checked-out script.

When you create a copy of a reposited script, the copy opens in JD Edwards Autopilot. The window title bar contains the word Repository, and the title and description of the reposited script.

If you modify the copy and then click Save, JD Edwards Autopilot displays an error message indicating that the script is not checked out and that you must either check it out or save it as a local file before the changes take effect.

Checkout Command

You might retrieve a script from the repository to modify it. To do so, you must check out the script, make and save the changes, and then check it back into the repository. JD Edwards Autopilot returns the script to the repository with the changes intact. The repository then contains a new version of the script.

When you check out a script from the repository, you check out the latest version of the script. A script cannot be checked out to more than one person at a time. This prevents two people from making changes to the script simultaneously.

You can also run the Checkout command when you are browsing scripts. In the Select Script form, you can limit the script search by selecting options and entering information on the various tabs.

Undo Checkout Command

You can undo the Checkout command if, for example, you change an existing script but decide to cancel the changes. If you check in the script, the changes take effect, and the repository contains a new version of the script. If you use the Undo Checkout command, none of the changes that you make to the script take effect. To undo the checkout, select File, Repository, Check In/Check Out, Undo Check Out. A form confirms the undo checkout.

My Checkouts Form

You can find scripts that you have checked out by using the My Checkouts form. The My Checkouts form enables you to keep track of the scripts that you check out to ensure that you check them back in. The My Checkouts form contains the same headings as the Browse Scripts form. Each document button next to the script title displays a green check mark, which indicates that you have checked out the script on the machine that you are currently using.

You cannot check out a script on one machine and check it in on another. The My Checkouts form displays all of your checkouts on the current machine. If you check out a script on a machine other than the one on which you are currently working, the document button next to the script title contains a red X, which indicates that you cannot check in the script from the current machine.

Check In Command

After you check out a script, you can make any necessary changes to the reposited version. When you are finished with the changes, you must check in the script for them to take effect. When the script is checked in to the repository, the new version is available to other people. When you check in a script, it automatically closes and enters the repository, just as when you add a script to the repository.

Where Included Command

You sometimes need to determine if a script is included by another script, because you cannot delete an included script. You can use the Where Included command to search the repository for all scripts that include another script.

When you enter the title of a script, the Where Included form displays the titles and descriptions of any reposited scripts that include the script title.

From the Where Included form, you can select a script and create a copy of it or check it out. The script that you select from this form is a master script; it is the parent of the script for which you initially searched, as well as for any other scripts that might be included with it. If no scripts appear in the Where Included form, you can delete the script.

Working with the Script Repository

This section provides an overview of the script repository and discusses how to:

• Assign properties to a script.

• Add a script to the repository.

• Browse for repository scripts.

• Delete a script from the repository.

• Assign security to a reposited script.

• Get a copy of a script.

• Check out a script.

• Undo script checkout.

• Check in a script.

• Query for included scripts.

• Use a Command Line to Load a Repository Script.

Understanding the Script Repository

The JD Edwards Autopilot script repository enables you to retrieve scripts for study, playback, and modification. You can add scripts that you create, and others can retrieve copies to review the functions that you tested or to use a script as a template for another script. In turn, you can retrieve other people's scripts for the same purpose. You can also check out scripts from the repository, change them, and store the new versions by checking them in.

The script repository works in conjunction with the other components of JD Edwards Autopilot. After you have written a script, you can assign properties to it and save it locally. When you add it to the repository, you make it available to others in a centralized storage location, and it becomes a controlled version that can be changed only by following prescribed procedures.

Assigning Properties to a Script

Before you add a script to the repository, you can assign properties that remain with it when you save the script. Properties include the script title, description, main application tested, and other parameter values that you assign to it. These identifying features facilitate searches of the repository for scripts of a specified type. You save the property pages locally along with the script.

To assign properties to a script:

1. From the JD Edwards Autopilot window, open a script.

2. In the File menu, select the Properties option.

   The Script Properties form appears.

3. In the Script Properties form, enter information or select options in the fields on each of these tabs:

   • General

   • Details

   • Comments

   • Categories

4. Click OK.

5. In the File menu, select Save or Save As and assign a title that follows your predetermined naming convention.

Adding a Script to the Repository

After you save a script (and any assigned properties), you can add it to the repository. The script must be open before you can add it. When you select the Add to Repository command, JD Edwards Autopilot enables you to assign script properties for the first time or to modify previously assigned properties. After you add the script to the repository, JD Edwards Autopilot identifies the script by the title and description that you enter.

To add a script to the repository:

1. In the JD Edwards Autopilot window, open the script that you want to add to the repository.

2. In the File menu, select Repository, Add to Repository.

   The Add Script to Repository form appears.

3. On the Add Script to Repository form, enter any script properties that you want to assign.

4. Click OK.

   JD Edwards Autopilot closes the script and checks it into the repository. A controlled copy of the script now exists in the repository. You can still change the local copy.

Browsing for Repository Scripts

You can browse the repository for scripts to run, use as a template, or modify. You can view all of the scripts in the repository or enter search criteria in the Select Script form to search for scripts of a certain type. You enter information and select options to establish search criteria. JD Edwards Autopilot uses the criteria to display any scripts that have matching properties.

To browse for scripts:

1. In the File menu of the JD Edwards Autopilot window, select Repository, and then Browse Repository Scripts.

   The Select Script form appears. The form contains the same four tabs that appear on the Script Properties form and the Add Script to Repository form.

2. On the Select Script form, establish criteria for the scripts to retrieve.

3. Click OK.

   The Browse Scripts form appears and displays the titles of the scripts that match the specified criteria.

Deleting a Script from the Repository

You can delete a script from the repository if you are its owner or you have the proper authorization. As a precaution, JD Edwards Autopilot prompts you to first confirm the delete.

Note. You cannot delete a script if it is included in another script.

To delete a script from the repository:

1. In the File menu of the JD Edwards Autopilot window, select Repository, and then Browse Repository Scripts.

2. On the Select Script form, enter your user ID in the Owner field on the General tab and click OK.

   Note. If you are authorized to delete scripts other than those that you own, you can use other selection criteria by completing additional controls and options on the tabs of the Select Script form.

3. On the Browse Scripts form, select the title of at least one script that you want to delete from the repository and click the Delete button.

   A JD Edwards Autopilot window prompts you to confirm the deletion of the script. If you click Yes when the script is open, JD Edwards Autopilot closes the script.

4. Click OK.

   Note. The deletion fails if the script is included in another script.

Assigning Security to a Reposited Script

After you add a script to the repository, you can assign security to it, or you can leave it unsecured. Assigning security to a script restricts other people's access to it.

You can assign security to a script if you are not its original owner, but only if the original script has no restrictions. However, you must make yourself the owner of the script before you can change its security.

Note. You can also assign security to a script by using the My Checkouts form if you have checked out the script from the repository.

To assign security to a reposited script:

1. In the File menu of the JD Edwards Autopilot window, select Repository, and then Browse Repository Scripts.

2. On the Select Script form, enter your user ID in the Owner field on the General tab and click OK.

3. On the Browse Scripts form, select one or more scripts and right-click.

   The system displays a pop-up menu that contains four security-level options.

4. From the pop-up menu, select one of these security levels:

   • No Restrictions

   • Owner Locked

   • No Checkout/in

   • No Access

Getting a Copy of a Script

You can use the Browse Scripts form to create a copy of a script to play back or to use as a template for creating another script. Note these points about script copies:

• You can change the copy, but you can save the changes only to a separate local copy of the script, not to the reposited script.

• You cannot create copies of more than one script if one of the scripts that you select is checked out.

• If you select only the checked-out script, you create a copy of the script, including the changes made since the last checkout.

To create a copy of a script:

1. From the File menu of the JD Edwards Autopilot window, select Repository, and then select Browse Repository Scripts.

2. On the Select Script form, establish criteria for the types of scripts to retrieve.

3. Click OK.

4. In the Browse Scripts form, select at least one script.

5. Click the Get Copy button.

Checking Out a Script

You can check out scripts that are added to the repository. Only one person at a time can check out a script. You can make changes to a script that you check out, and then check it back in. JD Edwards Autopilot saves all changes and creates a new version without prompting you to add the script to the repository.

If someone has checked out a script, the document button next to the script title in the Browse Scripts form contains a check mark or an X. An X appears if a script has been checked out to another computer. If you attempt to select multiple scripts and one of them has already been checked out, JD Edwards Autopilot disables the Get Copy and Checkout commands. If you select the checked-out script only, you can open the script to check it into the repository or to undo the checkout.

To check out a script:

1. From the File menu of the JD Edwards Autopilot window, select Repository and Browse Repository Scripts.

2. On the Select Script form, establish criteria for the types of scripts to retrieve.

3. Click OK.

4. On Browse Scripts, select one or more scripts; and then click Check Out.

Undoing Script Checkout

You can undo a script checkout if, for example, you make changes to the script but then decide not to save the changes.

To undo a script checkout:

1. From the File menu of the JD Edwards Autopilot window with a checked-out script open, select Repository, Check In/Check Out, Undo Check Out.

   A JD Edwards Autopilot window appears prompting you to confirm the checkout cancellation.

2. Click Yes.

Checking in a Script

If you check out a script and make changes to it, you can check it back in to save the changes in the repository.

From the File menu of the JD Edwards Autopilot window, with a checked-out script open, select Repository, Check In/Check Out, Check In.

Note. You can identify all of the scripts that you have checked out by selecting File, Repository, My Checkouts.

The script closes. JD Edwards Autopilot checks in the new version of the script.

Querying for Included Scripts

You can use the Where Included form to search the repository for any scripts in which a particular script is included. If a script is included in another reposited script, you cannot delete it from the repository.

To query for included scripts:

1. From the File menu of the JD Edwards Autopilot window, select Repository, Where Included.

2. On the Where Included form, enter the title of a script and click OK.

   JD Edwards Autopilot displays the titles of all scripts that include the script for which you entered the title. You can check out or create a copy of these scripts.

Using a Command Line to Load a Repository Script

You can load any repository script into JD Edwards Autopilot from a command line. The script command line parameter is passed in with an .atr extension. This extension is used to designate repository scripts.

The command line calls the JD Edwards Autopilot executable file and identifies the specific repository script to load into JD Edwards Autopilot. The .atr extension indicates to JD Edwards Autopilot that it must access the repository to retrieve and load the script that you entered in the command line. Enter the command as follows:

C:\Autopilot.exe MyRepositoryScript.atr

where MyRepositoryScript is the title of the repository script to be loaded.

Working with Script Reporting

This section provides an overview of script reporting and discusses how to:

• Use the event stream.

• Use the Test Results form.

Understanding Script Reporting

The script repository contains information about scripts that test particular applications and processes. The architecture of JD Edwards Autopilot also contains a results repository, the F97214 table. This repository contains information about the actual JD Edwards Autopilot and JD Edwards EnterpriseOne events that occur during script playback.

If you configure JD Edwards Autopilot to capture and store playback events, it records each event using internally placed code and code in JD Edwards EnterpriseOne software. When playback finishes, JD Edwards Autopilot sends the record of events, called the event stream, to the repository. You can view each event stream on the Test Results form.

Using the Event Stream

The event stream provides a timeline of the events that occurred during script playback. For example, you can see which tables were opened, which business functions were called, which event rules were invoked, and the time required to complete each event. You can also identify error and warning messages that appeared. This information enables you to troubleshoot problems that occur during playback.

You also capture an event stream when you want to use JD Edwards Virtual Autopilot to generate a virtual script that you can use to simulate multiple users on a single workstation.

Important! JD Edwards Virtual Autopilot requires a JD Edwards EnterpriseOne Windows client. You can use JD Edwards Virtual Autopilot with JD Edwards EnterpriseOne Tools 8.97 and JD Edwards EnterpriseOne Applications 8.10 and prior. You cannot use JD Edwards Virtual Autopilot with JD Edwards EnterpriseOne Applications 8.11 and later releases, as these releases are on a web client only.

Using the Test Results Form

If you have configured script playback to capture, save, and display results, the Test Results form appears when playback finishes. The Test Results form displays playback data such as the event stream, which is a chronological listing of each event that occurs during playback. You can filter the list for test time, type, or text. You can also view previous test results, and you can review details about the results.

The Test Results form contains these tabs:

• Browse Result Sets

• Summary

• JDE.INI

• JDE.LOG

• JDEBUG.LOG

• Screen Captures

• Messages

• Results

Browse Result Sets Tab

The Browse Result Sets tab contains summaries of all the tests for which you have saved results. You can also view the events in an individual test. A check mark beside a test indicates that it was successful; an X indicates a test that failed or was canceled.

The Test Results form for saved tests also permits you to print results and to export them to a spreadsheet using buttons at the bottom of the form. The Filter button enables you to filter the saved test results using the columns in the form as criteria. You use the Filter form to select a filter criterion.

Summary Tab

Clicking the Summary tab displays these properties for each test that you run:

• Script

• Machine

• Release

• Environment

• User

• Start time

• End time

• Elapsed playback time

• Status of the playback

JDE.INI Tab

The JDE.INI tab enables you to view the initialized settings for JD Edwards EnterpriseOne software that existed before JD Edwards Autopilot played the script. JD Edwards Autopilot captures the file from C:\Winnt\JDE.INI, and then displays its contents on the tab. You can troubleshoot the file to see, for example, whether paths in the JDE.INI setting point to the correct database or drive. You can also use data on the JDE.INI tab to duplicate the results of one test in another.

Jde.log Tab

After script playback, JD Edwards Autopilot captures the jde.log file from C:\jde.log and displays it on the jde.log tab of the Test Results form. You can view the contents of the file to track errors that occur during processing.

Screen Captures Tab

If a script fails, JD Edwards Autopilot captures the screen that is active when the script fails and lists the screen shot on the Screen Captures tab.

Jdedebug.log Tab

The jdedebug.log tab displays the jdedebug.log file that JD Edwards Autopilot captures from the C:\jdedebug.log file after it completes script playback. You can troubleshoot the file to determine, for example, when normal execution of the script stopped. You can also review the timing of all processes that occur during script playback.

Messages Tab

Data that appears on the Messages tab of the Test Results form summarizes the script that JD Edwards Autopilot played back.

You can review each context command and action command that you write in the script, as well as any error messages that JD Edwards Autopilot generates. In addition, you can review any error messages that JD Edwards EnterpriseOne software generates during playback.

On the Messages tab, you can filter, print, and export test results. You can filter test results for:

• A particular point during playback that an event occurred

• A particular type of event, such as a message or an action in JD Edwards Autopilot

• A text description of the event in the Test Results form

You can print the test results, provided that you have set up a default printer to do so. Using the Export button, you can export test results to a spreadsheet.

Results Tab

When a script finishes, you can see the results on the Messages tab in a grid format. The Results tab contains those same results in an enhanced tree control format that enables you to view individual events. You can use this tree control format to assist in troubleshooting. For example, if you are searching for errors in a script, you can identify them by the red exclamation marks next to the events.

See Also

Options for Configuring JD Edwards Autopilot in the JD Edwards EnterpriseOne Autopilot Guide

Results in the JD Edwards EnterpriseOne Autopilot Guide

Working with JD Edwards Autopilot Test Manager

This section provides an overview of Test Manager and discusses how to:

• Use the script display pane.

• Use the script storage pane.

• Use the test results pane.

• Use the Test Manager toolbar.

Understanding Test Manager

JD Edwards Autopilot Test Manager enables you to test multiple JD Edwards Autopilot scripts in a batch, so that you can review results quickly and gather test results for archiving. You use Test Manager to create a playlist that contains scripts that you save on your local drive, scripts that you retrieve from the script repository, or a combination of both.

After you assemble a playlist, you run it. Test Manager launches JD Edwards Autopilot, which in turn launches JD Edwards EnterpriseOne software. Test Manager runs the playlist to completion, closing JD Edwards Autopilot each time a script completes and opening JD Edwards Autopilot immediately after the next script appears in the queue. Test Manager displays a test status of Failure, Success, or Incomplete for each script that runs.

You can view the results of each script playback. These results include messages that enable you to analyze the cause of a script failure. In addition, you can save the playlists that you create, edit them, and replay them.

Using the Script Display Pane

The script display pane in Test Manager is the area where you select scripts to assemble a playlist. The pane contains two tabs, Local and Repository. When you select the Local tab, Test Manager displays all the scripts that you have stored on the local drive.

When you select the Repository tab and then click the Repository Filter button, Test Manager launches the Select Script form, which you can use to enter search criteria for scripts that have been checked in to the repository.

Test Manager populates the script display pane with the names of the scripts that match the property criteria that you enter in the Select Script form. You can add these scripts to the playlist in the script storage pane.

Note. Test Manager creates copies of the repository scripts. It does not check out scripts from the repository. Adding a reposited script to the Test Manager playlist does not prevent other users from checking out the script from the repository and changing it.

See Also

Property Pages for Scripts

Assigning Properties to a Script

Using the Script Storage Pane

You add scripts from the script display pane to the script storage pane to create a playlist. When you initially add scripts to the script storage pane, Test Manager displays the state of the script as Idle, which means that you have added it to the playlist but have not yet run it.

You can remove scripts from the script storage pane. When you remove a script from the playlist, Test Manager prompts you to confirm the action.

After you assemble the playlist, you run it by clicking the Run button on the toolbar. Test Manager launches JD Edwards Autopilot and runs the scripts in the order that they appear in the script storage pane. After the script runs, Test Manager displays one of these states, depending on the results of the test: Success, Failure, Cancellation, or Incomplete.

Using the Test Results Pane

After you have assembled and run a playlist, Test Manager summarizes the results in the test results pane. You can review the summary by clicking the Report button on the toolbar. The test result summary displays this information about the test:

• Total number of tests generated.

• Status breakdown, including the number of scripts that failed, succeeded, were canceled, or did not finish.

• Name of the client machine.

• Environment in which the test was run.

• Release in which the test was run.

• Name of the script.

• Number of the test.

• Status of each script run.

• Time elapsed for each script run.

• Comments that you added to the script and designated for logging in Test Manager.

If a script fails, click the Report button to display message types in the test results pane, along with the time of the message. These message types provide information about why the script failed, as well as information about warning messages that might have appeared during playback.

In addition, Test Manager provides information about warning messages. This table lists some of the message types that can appear in the test results pane and summarizes their meanings:

Using the Test Manager Toolbar

The Test Manager toolbar enables you to control a test session and view its results. The Test Manager toolbar contains these buttons:

Managing Script Testing

This section provides an overview of script testing and discusses how to:

• Create a playlist.

• Save a playlist.

• Run a test.

• View test results.

• Reset a test.

Understanding Script Testing

You use JD Edwards Autopilot Test Manager to create a playlist from scripts that reside on your local drive or in the script repository. Test Manager enables you to run a playlist multiple times, without intervention. The playlist can contain a combination of local and reposited scripts. You can save a playlist, or you can reset it and play it again from the top. You can view the summarized results of each playback in the test results pane, collected playback results, or the events of an individual test.

Creating a Playlist

The first task in Test Manager is to create a playlist. You retrieve the scripts for your playlist from your local drive, the script repository, or both. The Add button on the toolbar enables you to move scripts from the script display pane to the script storage pane, where the playlist resides.

To create a playlist:

1. On the desktop or in the directory where you store Test Manager, click the Test Manager executable file.

   The Test Manager splash screen appears, followed by the JD Edwards Autopilot Test Manager form.

   Note. When the Test Manager form appears, the script display pane and the script storage pane might not appear. Drag the splitter bar that separates them by using the grabber, which is represented by a pair of vertical bars.

2. In the script display pane of the JD Edwards Autopilot Test Manager form, select either the Local or the Repository tab.

3. If you select the Local tab, select a local script from the script display pane and click the Add button on the toolbar.

   Test Manager adds the selected test to the script storage pane.

   Note. You can select more than one test by selecting a script in the script display pane, holding down either the Ctrl or the Shift key, and selecting additional scripts.

4. Select the Repository tab.

5. Click the Repository Filter button.

   Test Manager displays the Select Script form.

6. In the Select Script form, select script criteria to narrow the number of scripts that you copy from the repository, and then click OK.

   Test Manager displays in the script display pane any repository scripts that match the search criteria.

7. Select one or more repository scripts from the script display pane, and then click the Add button on the toolbar.

8. Continue adding local and repository scripts until you have created the playlist.

9. To change the sequence of the scripts, click a script in the script storage pane and click the Up or Down button on the toolbar.

10. To remove a script from the playlist, select it in the script storage pane and click the Remove button on the toolbar.

Saving a Playlist

After you create a playlist, you can save it, or you can run the test before you save it. Remember, if you do not save the playlist, Test Manager prompts you to do so when you exit the form.

To save a playlist:

1. In the File menu of the JD Edwards Autopilot Test Manager form, select Save or Save As.

2. Assign the playlist a filename and save it to a drive and directory, and click Save.

   Note. Test Manager assigns to all playlists the default extension of .apl.

Running a Test

After you create a playlist, you can run the test. Test Manager launches JD Edwards Autopilot, and then runs each script in the queue in the order that you set up in the script storage pane.

Test Manager launches JD Edwards Autopilot, minimizes the JD Edwards Autopilot window, and then begins running the first script in the queue. As each test finishes, Test Manager displays its result in the script storage pane. When Test Manager finishes running a script, it closes JD Edwards Autopilot, and then relaunches it with the beginning of the next script in the queue.

As each script finishes running, Test Manager displays the result of Success, Failure, Canceled, or Incomplete.

To run a test:

1. In the File menu of the JD Edwards Autopilot Test Manager form, select Open.

2. Open the drive, directory, and file in which you store your playlists, select one or more playlists, and click Open.

3. On the toolbar of the JD Edwards Autopilot Test Manager form, click Run.

   Note. During playback, JD Edwards EnterpriseOne software remains open, unless a script contains an Exit JD Edwards command, in which case the software closes. In this case, with the beginning of the next script in the queue, JD Edwards Autopilot Test Manager launches JD Edwards Autopilot, which launches JD Edwards EnterpriseOne software.

4. To stop the test, click the Stop button on the toolbar.

Viewing Test Results

After Test Manager completes the playlist, you can review the playback results in one of two ways. Click the Report button to review in the test results pane a summary of the results from the current playlist. To view summaries of the tests from all the playlists that you run and save, click the Log button.

To view test results:

1. On the JD Edwards Autopilot Test Manager form, open a saved playlist.

2. After JD Edwards Autopilot Test Manager completes the playlist, click the Report button on the toolbar.

   Test Manager populates the test results pane with a summary of the results for each script in the playlist.

3. To view summaries of all scripts that you have played back, click the Log button on the toolbar.

   Test Manager displays the Test Results form, which contains summary information about the results of all played-back scripts.

4. To view in detail all the events for the playback of an individual script, select the script on the Test Results form, and then select the Results tab or the Messages tab.

Resetting a Test

After you assemble a playlist and run it, you can reset the test, which overwrites the previous results. Resetting might be appropriate if scripts in the original test fails and you make changes to correct the failure.

To reset a test:

1. On the JD Edwards Autopilot Test Manager form, open a playlist that you have already run.

2. On the toolbar, click the Reset button.

   If Test Manager displays a form warning you that resetting the test overwrites the existing results, click Yes.

3. On the toolbar, click the Run button to rerun the test