18 Using the STAP Design Experience Package

This chapter details how you can use the Oracle Communications Solution Test Automation Platform Design Experience Package to simplify the end-to-end automation process.

Topics in this document:

Automating Using STAP Design Experience

The STAP Design Experience (DE) package simplifies the automation of end-to-end scenarios by offering a user-friendly Behavior-Driven Development (BDD) environment for creating, testing, and deploying automation. It includes streamlined scripts for compiling, running, and publishing automation, along with a sample workspace featuring diverse examples across various plugins. Additionally, the package provides ready-to-use environment templates tailored for specific plugins and environments to accelerate the automation process.

Before using the STAP Design Package, ensure you have set it up on your system. For more information, see "Setting Up The STAP Design Experience" in Deployment Guide.

The following is an end-to-end process of how to set up and run automation using the STAP Design Experience Package.

Caution:

Ensure you have securely stored your automation project in a third-party version control that includes initializing a repository, tracking changes, and collaborating efficiently.
  1. Create an Automation Workspace: Create a dedicated folder within your project to serve as the automation workspace. STAP offers two ways to configure folder paths:
    • Configuration Folder: Create a config folder within the workspace. This folder contains the primary configuration file config.properties, which STAP run time uses to load other configurations. For more information, see "Configuration Folder". Create subfolders within the config to organize other configurations.
    • (Optional) Environment Configurations: Create an environments subfolder within the config. If you have multiple environments, inside each environment folder, create separate property files for each product API. If you only have one environment, create all environment property files directly under the environments folder. Update the config.properties file with the environment configuration location. For more information, see "Environments Folder".
  2. Results Folder: STAP stores execution results in the results folder. The path can be relative to the workspace or an external location. Execution results are stored in timestamped folders under <workspace>/results/. You open report.html within each result folder to view the execution report. Configure the results storage location in config.properties. For more information, see "Results Folder".
  3. Context Folder: The context folder stores test context data used during scenario development. Context helps visualize variables and their values used in each step. It allows executing specific steps while simulating previously run ones using the context. Configure the context storage location in config.properties. For more information, see "Context Folder".
  4. Scenarios Folder: Define the location of the scenarios folder in config.properties. Each scenario is stored in a separate folder within this directory. For more information, see "Creating Scenarios".
  5. Compile and Run Automation: Use the Command Line Interface to compile and run automation. For more information, see "Publishing Data using Command Line Interface".
  6. View Reports: You can view the reports of the scenarios run in the Results folder. For more information, see "Results Folder".
  7. Publish Scenarios: Once the automation is complete, you can publish scenarios. For more information, see "Publishing Data using Command Line Interface".