OpenText Octane

OpenText Octane test repository adapter for ABAP Agent 2.0 — CLI and Guides references.

Use adapter type octane to connect OpenText ALM Octane (formerly Micro Focus ALM Octane) so the agent can search manual tests in an Octane workspace.

This adapter is separate from alm (OpenText ALM), which connects to the on-premises OpenText ALM / Quality Center client stack.

When you create the ABAP pipeline with pipeline set, leave --labid unset unless you deliberately need to override it. The agent derives the default lab ID as <QAS SID> <QAS RFC hostname>. Casual overrides can break Test Cycles in SeaLights. See Create and list pipelines.

Configure

• Configure Test Repositories — slabapcli testrepo set --type octane
• Setup and installation (Part 1)
• Show the value with Test Cycles (Part 2)

testrepo set parameters for octane

Non-secret keys use --setting key=value. Secrets are entered interactively (not via --setting). Plus common options (--name, --type, --pipeline, --test-stage) — see Configure Test Repositories.

Authentication uses OAuth client credentials: apikey (client id) and apisecret (client secret).

Parameter	Kind	Required	Description
url	Setting	Yes	Octane REST base URL (for example http://octane.example.com:8080).
sharedSpace	Setting	Yes	Octane shared space name.
project	Setting	Yes	Octane workspace name.
searchPaths	Setting	No	Comma-separated list of Octane application module names that scope the search. Written as top-level searchpaths in config.toml. When omitted, the adapter searches the entire workspace.
confidenceThreshold	Setting	No	Integer 0–100. Minimum confidence for a match. When omitted, the adapter uses 0.
apikey	Secret	Yes	Octane OAuth client id (apikey).
apisecret	Secret	Yes	Octane OAuth client secret (apisecret).

Command Prompt

Command

slabapcli.exe testrepo set --name "ALM_Demo-octane" --type "octane" --pipeline "ALM_Demo-S21" --setting url=http://octane.example.com:8080 --setting sharedSpace=MySharedSpace --setting project=SAP_Workspace1 --test-stage "Regression Tests"

PowerShell

Command

.\slabapcli.exe testrepo set --name 'ALM_Demo-octane' --type 'octane' --pipeline 'ALM_Demo-S21' --setting url=http://octane.example.com:8080 --setting sharedSpace=MySharedSpace --setting project=SAP_Workspace1 --test-stage 'Regression Tests'

--test-stage is optional. See Configure Test Repositories for the default "{type} Tests" value, clear-on-omit behavior, and duplicate-stage warning.

The CLI prompts for apikey and apisecret interactively (OAuth client credentials; secrets are not accepted via --setting).

Expected output (PowerShell, abbreviated)

.\slabapcli.exe testrepo set --name 'ALM_Demo-octane' --type 'octane' --pipeline 'ALM_Demo-S21' --setting url=http://octane.example.com:8080 --setting sharedSpace=MySharedSpace --setting project=SAP_Workspace1 --test-stage 'Regression Tests'
[2026-03-08 10:45:00.123+02:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
Enter apikey: **********
Confirm apikey: **********
Enter apisecret: **********
Confirm apisecret: **********
Configuration for adapter 'ALM_Demo-octane' was saved successfully.
Running connection test for 'ALM_Demo-octane'...
Connection test passed for 'ALM_Demo-octane' (pipeline: 'ALM_Demo-S21').

Once the test repository is configured and the connection test succeeds:

1. Finish any remaining agent setup for the pipeline (RFC, pipeline, additional test repositories) if you have not already.
2. Schedule repository search with search_testrepo.
3. Capture coverage with Footprints and your test runs.

For the full setup order, see Start the ABAP Agent Server and Configure Test Repositories.

search_testrepo registers a Windows Scheduled Task that runs watcher.exe SEARCH_TESTREPO on a cron schedule.

Command Prompt

Schedule a search

slabapcli.exe search_testrepo run --pipeline <pipeline> --testrepo <name> [--cron "<cron>"]

PowerShell

Schedule a search

.\slabapcli.exe search_testrepo run --pipeline <pipeline> --testrepo <name> [--cron '<cron>']

Parameter	Required	Description
--pipeline	Yes	Pipeline name ([[pipeline]].name).
--testrepo	Yes	Test repository name ([[testrepo]].name) linked to that pipeline.
--cron	No	5-field cron expression in the machine's local time. Default: 0 2 * * 0 (Sunday at 02:00). Supported forms: M * * * *, */N * * * *, M/N * * * *, M H * * *, and M H * * D (D is one day, 0-7 or SUN-SAT). Ranges and lists (for example 1-5) are not supported, and day-of-month and month must be *.

Full command reference (stop, list, prerequisites): Search Test Repositories.

SeaLights associates test executions with ABAP code changes through Footprints on the agent side.

1

Schedule Footprints for the pipeline

slabapcli.exe footprints run --pipeline <pipeline-name>

This creates a FOOTPRINTS scheduled task that periodically collects coverage-related data and sends it to SeaLights. Full syntax and stop command: Collect Footprints data for your Pipeline.

2

Run tests against the QAS system

Execute tests that exercise the ABAP components you care about while Footprints is collecting. The agent matches executed ABAP components against objects in the latest Build Modification and reports them as footprints.

3

Wait for processing, then check the Coverage Report

SeaLights needs time to process Footprints data. When processing completes, covered ABAP components appear in your application's Coverage Report.