Skip to main content

Test Execution

Executing Worksheets​

To execute a worksheet manually:

  1. Open the worksheet from the Worksheets page.
  2. Click on Run Worksheet. A dialog opens.
  3. Optionally, you can modify the following settings:
    • Run definition
      • Name: The name of this test run. By default, it has the form "(Worksheet) - (Date)".
      • Start URL: This URL will be set as the base URL. It represents the starting point of the application.
      • Conversion: The version of the worksheet to execute. Choose Latest possible to create a new version if the worksheet has changed since the last version or to execute the newest one otherwise. Choose the version number if you want to execute a specific version.
      • Engine: The browser engine to use.
      • Execute immediately: If Yes, the worksheet will be run as soon as a test runner is available. If No, you can plan the execution for a specific date and time.
      • Worksheet Variable Set: You can choose a Variable Set for execution. Keep this setting empty to let LCT choose one randomly.
        • This setting will only be displayed if at least one Variable Set is defined in this worksheet.
        • Read more about Variables and Variable Sets.
    • Execution Settings
  4. Click on Run to start the test.
    • If you choose not to execute the worksheet immediately, this button changes its text to Schedule.

A Queue entry will be created for this execution. You will be redirected to the Queue page with this entry being selected.

note

A Worksheet is able to run if:

  1. It is not empty (does have at least one standard case)
  2. It does not only consist of deleted standard cases
  3. It does not only consist of disabled standard cases
  4. Its cases are not all empty (not having any steps)

Executing Test Suites​

Test Suites executions can be triggered manually or by the scheduler at regular intervals.

Read more about Test Suites.

Inspect the Queue​

Queue grid​

The grid contains various columns to facilitate customization.

General:

  • Actions
    • Execution Details: Opens a dialog where information about each test case of this run is listed
    • Go to Worksheet: Redirects to the edit page of this worksheet
    • Version Details: Displays the generated Playwright code of the current test version
    • Test Files: Lists all files that were created for or by the test runner
    • Rerun test: Schedules this worksheet for a manual execution
  • Queue ID
    • The unique number that identifies the Queue entry in the current instance
  • Execution Name
    • For worksheet executions, the name that was chosen in the Schedule Test dialog. By default, it has the form "(Worksheet) - (Date)".
    • For Test Suite executions, the name has the form "(Test Suite) - (Worksheet) - (Engine)".
  • Worksheet Name
    • The name of the worksheet being executed
  • Version
    • The conversion number of the worksheet

Execution:

  • Engine
    • The browser engine used for this test
  • Execution Point
    • The timestamp when the test was scheduled
  • Status (Icon)
    • An icon representing the state of this entry
  • Status
    • scheduled: The worksheet is scheduled for execution
    • running: The worksheet is being executed now
    • completed: The execution has finished and results are available
    • error: There was an (technical) error while executing the worksheet
  • Successful/Total Cases
  • Successful Cases
  • Failed Cases
  • Total Cases
  • Test Successful
    • Yes if all test cases were successful
    • No if at least one test case has failed
  • Execution Time
    • The total execution time, in the format min:sec
  • Execution Time (Seconds)
    • The total execution time, in seconds
  • Output Log
    • Opens the Output log where all test case results and screenshots are displayed. Also, the raw log can be reviewed.
  • Test Suite Name
    • If this worksheet is executed as a part of a Test Suite run, its name is listed here.

Audit Values:

  • Created By
    • The user which triggered this test. It can be a regular LCT or an API user. If the current entry is added by the Test Suite scheduler, LCT_TEST_SUITE is used.
  • Created On
    • The timestamp when the Queue entry was created. It does not need to match the actual execution time.

We recommend reading the Use Interactive Grids section of the Oracle APEX documentation to learn more about Interactive Grid usage and customization.

Live log​

note

The live log feature is disabled by default. To enable, go to Administration > Settings and set Enable Livelog to Yes.

Each user can choose to enable or disable the live log individually. To change this setting, click on your username in the navigation bar and choose Preferences. Now, you can change the Livelog Enabled setting. Save the changes and reload the page to apply.

The live log shows the output of the test runner in real time. This will be indicated by a yellow dot in the top right corner. In this way, you can follow the progress of your worksheet execution.

If the worksheet has finished its execution, no yellow dot is visible, and the raw output log will be displayed.

To choose which log should be displayed, simply select a cell of the corresponding entry in the grid.

Common Test Files​

This is a list of files that are generated by the test runner:

File nameDescription
lct.spec.jsPlaywright code generated by the converter
lctReporter.jsSource code for our custom Playwright reporter
output.logThe raw output log created by our custom reporter
playwright.config.jsContains settings for the test runner, mostly execution settings
pwUtils.jsContains functions for interaction with APEX components
results.xmlJUnit xml report generated by the JUnit Playwright reporter
screenshots/...Screenshots of screenshot steps
traces/.../test-failed-1.pngScreenshots automatically created by Playwright if a test fails
var_utils.jsContains functions for handling variables