Note that many menu commands in the Test Editor are specific to the currently selected step.
Test Editor PTF Menu Commands
This table describes the Test Editor PTF menu commands:
PTF Menu Commands Usage
Projects Opens the Projects dialog box.
Local Options Open the Local Options dialog.
Execution Options Open the Execution Options dialog.
Test Editor Test Menu Commands
This table describes the Test Editor Test menu commands:
Test Menu Commands Usage
Save Saves the current test.
Save As Creates a copy of the current test with a new name.
Test Menu Commands Usage
Test Case Save As Creates a test case as a copy of the current test case.
Export Export test cases and test case values to a character-delimited
text file, such as comma-separated values (csv) file.
Import Import test cases and test case values from a
character-delimited text file, such as comma-separated values (csv) file.
Copy Link to Clipboard Copies a link to the test to the clipboard.
You can send this information to another user, who can use the Window, Quick Open feature to open the test without having to navigate to it in PTF Explorer.
Validate Test Validate the test against the application metadata to identify changes in the metadata since the test was last modified. As you modify a test based on the results of a test maintenance report, you can validate the test by running a test maintenance report. The report is generated for a single test, using analyses of compare reports generated in Step 2 of the Test Maintenance Wizard.
See Creating Test Maintenance Reports.
Check Syntax Validates the parameter syntax and values.
See PTF Test Language
Run Runs the current test.
Run from Step Runs the current test from the specified line number.
Pause Pauses execution of the test.
End Stops execution of the test.
Open Test Recorder Launches the Test Recorder.
Test Editor Edit Menu Commands
The Test Editor Edit menu contains standard Microsoft edit commands, such as Cut, Copy, Paste, and Delete, and the following PTF commands:
This table lists the additional PTF commands:
Edit Menu Command Usage
Find Finds occurrences of a specific text string in the current test.
Select the List all Matching Steps check box to create a list of matches.
Again Searches for the Find string again.
Test Editor Debug Menu Commands
This table describes Test Editor Debug menu commands:
Debug Menu Command Usage
Step Into Executes the current step of the test and advances to the next step.
Step Over Executes the current step of the test and advances to the next step, unless the next step calls another test. Steps over called tests.
Toggle Break Sets a break point at the selected step or removes an existing breakpoint.
Clear All Breaks Removes all break points.
Stop on Error Stops execution if the test encounters an error.
Note: This option can be also be enabled through the command line.
Disable Screen Shots By default, the recorder creates a screen shot with each error.
Select this option to save space in the log by not creating screen shots.
Highlight Errors Highlights errors in the log in yellow.
Overwrite Log If a log window is open after the most recent execution of a test, you can choose whether to append to the open log or overwrite the open log.
Select this option to overwrite the open execution log.
Debug Menu Command Usage
Leave Browser Open Keeps the PTF-launched browser window open after executing a test, to assist with debugging. Be aware that if many tests are executed with this option enabled, performance may degrade as the webdrivers used by PTF consume memory. Use the Kill Leftover Drivers option if performance is impacted.
Note: This option can be also be enabled through the command line.
Kill Leftover Drivers Closes open Test Framework browser windows, to release the memory that is used by their associated webdrivers. When the Leave Browser Open option is enabled, if performance issues arise, you can use Kill Leftover Drivers at any time to free up memory.
Enabling Debug Options from the Command Line
You can enable the Stop on Error and Leave Browser Open debug options from the command line by using the -SOE and -LBO parameters respectively.
These parameters are used when you execute a test from the command line using the PsTestFW command.
For Stop on Error (-SOE) parameter, you can specify True, False, or Not Set in the command line. The default value is Not Set.
The Stop on Error (-SOE) parameter is used as shown in the following example:
-CS=abc.us.oracle.com:443
Note: Using Stop On Error (-SOE ) parameter in command line execution will override the StopOnError execution action in shell tests script.
The override works as follows:
• If -SOE=True in command line and Execution.StopOnError = False in shelltest, the command line execution of the called test is stopped that encounters a Fail.
• If -SOE=False in command line and Execution.StopOnError = True or ALL in shelltest, the command line execution of the called test will continue if it encounters a Fail.
• If–SOE is not set, command line execution of the called test will continue based on the setting of Execution.StopOnError.
For details on StopOnError execution action, see Execution
For Leave Browser Open (-LBO) parameter, you can specify True or False in the command line. The default value is False.
All existing browsers will be terminated by default before execution when -LBO parameter is set in command line parameters, unless the -TL parameter is used in command line execution.
The Leave Browser Open (-LBO) parameter is used as shown in the following example:
-CS=slc10ybf.us.oracle.com:443
Test Editor Window Menu Commands
This table discusses the Test Editor Window menu commands:
Window Menu Command Usage
Quick Open Using information from the Copy Link to Clipboard
command, quickly opens a test without having to navigate to the log in PTF Explorer. You can also use this menu command to search for and open multiple tests, test cases, or text execution logs.
Close All Closes all windows.