Configure Test Repositories
A Test Repository is an external test management tool (such as Tosca, qTest, or Excel) that the ABAP Agent queries to find test cases that cover your ABAP changes. Each test repository is linked to a Pipeline and carries adapter-specific connection settings.
Create or Update a Test Repository
slabapcli testrepo set
Creates or updates a test repository adapter entry in config.toml. After saving the configuration, the command may run an automatic connection test. You can also verify connectivity later with testrepo test.
Prerequisite: Create a Pipeline (slabapcli pipeline set) before running testrepo set. The --pipeline value must match an existing [[pipeline]].name in config.toml.
slabapcli.exe testrepo set --name <name> --type <type> --pipeline <pipeline> [--setting key=value ...] [--test-stage <stage>].\slabapcli.exe testrepo set --name <name> --type <type> --pipeline <pipeline> [--setting key=value ...] [--test-stage <stage>]--name
-n
Yes
A unique name for this test repository entry (stored as [[testrepo]].name).
--type
-t
Yes
The adapter type. Supported values: ado, tosca, toscacloud, excel, xray, qtest, certify, ssm, alm.
--pipeline
-p
Yes
The pipeline name this test repository belongs to (must match a [[pipeline]].name value in config.toml).
--setting
—
See per-adapter tables
A non-secret adapter setting in key=value form. Repeat this flag for each key. Secrets are not accepted via --setting — they are entered interactively (see below).
--test-stage
—
No
Optional SeaLights test stage for this test repository (stored as top-level [[testrepo]].teststage). This is a dedicated option — do not pass it as --setting. When omitted on testrepo set, any previously stored teststage is cleared. When never set or cleared, the effective default is "{type} Tests" (for example qtest Tests or ado Tests). See Configuration settings for the TOML key.
How testrepo set replaces settings
Full replacement on every call: testrepo set replaces the entire [testrepo.settings] block, searchpaths, and teststage on every invocation. Any optional key you omit is cleared — omitting --test-stage clears a previously stored teststage. To make a partial change — for example, to update a single setting without re-entering all others — edit config.toml directly.
See Configuration settings for the full [[testrepo]] schema.
Duplicate test stages: If another test repository on the same pipeline already uses the same effective test stage, testrepo set emits a warning but still saves successfully. The warning asks you to confirm intent — a shared stage can be valid when multiple repositories intentionally contribute regression tests for the same RFC or pipeline context.
How secrets are entered
Secret keys (credentials) are never accepted via --setting. After the non-secret settings are validated, the command prompts you interactively for each secret field. Input is hidden and you must confirm each entry. If you skip an optional secret (for example, one half of a two-pair credential), press Enter at the prompt.
To change a secret without re-running the full command, use the interactive set commands, or edit the value directly in config.toml when it is stored as plaintext (key and iv in [settings] are empty). If a scheduled task may already hold the prior credentials, stop and start that task as needed.
Per-adapter setting keys
The --setting flag accepts only non-secret keys. The table for each adapter type lists all accepted keys, whether they are required, and the expected format.
searchPaths (optional for all types that accept it) scopes the search to a comma-separated list of repository or filesystem paths. When omitted, the adapter searches the entire test repository. confidenceThreshold (optional, integer 0–100) sets the minimum match confidence for a test case to be considered a match. When omitted, the adapter uses its default. Exception: ado does not accept confidenceThreshold.
qtest
url
Yes
URL string
The qTest Manager base URL (e.g. https://mycompany.qtestnet.com).
project
Yes
String
The qTest project name or ID.
searchPaths
No
Comma-separated list
Scopes the search to specific qTest modules or paths.
confidenceThreshold
No
Integer 0–100
Minimum confidence for a match.
Secrets (entered interactively):
username
Yes
The qTest user account name.
password
Yes
The qTest user account password.
tosca
url
Yes
URL string
The Tosca server URL.
project
Yes
String
The Tosca project name.
workstates
No
Comma-separated list
Test case workflow states to include in the search.
searchTransaction
No
true / false
Whether to search Tosca Transactions.
searchTestConfiguration
No
true / false
Whether to search Tosca Test Configurations.
searchTile
No
true / false
Whether to search Tosca Tiles.
searchApiTypeSapModule
No
true / false
Whether to search API-type SAP module test cases.
bufferPatterns
No
Semicolon-separated list
Regex patterns applied to buffer test case names.
parameterPatterns
No
Semicolon-separated list
Regex patterns applied to parameter names.
searchPaths
No
Comma-separated list
Scopes the search to specific Tosca paths.
confidenceThreshold
No
Integer 0–100
Minimum confidence for a match.
skipCollect
No
true / false
When true, the adapter skips the data collection step.
configurationPatterns
No
Semicolon-separated list
Patterns for filtering Tosca configurations.
Secrets (entered interactively — provide exactly one credential pair):
username
One of username+password or apikey+apisecret
Tosca username.
password
One of username+password or apikey+apisecret
Tosca password.
apikey
One of username+password or apikey+apisecret
Tosca API key.
apisecret
One of username+password or apikey+apisecret
Tosca API secret.
toscacloud
url
Yes
URL string
The Tosca Cloud base URL.
spaceId
Yes
String
The Tosca Cloud space ID.
scope
Yes
String
The Tosca Cloud scope (e.g. project or workspace identifier).
workstates
No
Comma-separated list
Test case workflow states to include in the search.
searchPaths
No
Comma-separated list
Scopes the search to specific paths.
confidenceThreshold
No
Integer 0–100
Minimum confidence for a match.
Secrets (entered interactively):
clientId
Yes
The Tosca Cloud client ID.
clientSecret
Yes
The Tosca Cloud client secret.
excel
filePath
Yes
File path (.xlsx, .xlsm, or .xls)
Path to the Excel workbook on the agent host.
sheetName
Yes
String
The worksheet name that contains the test case data.
testCaseIdColumn
Yes
String
Column address for the test case ID (for example A).
testCaseNameColumn
Yes
String
Column address for the test case name (for example B).
searchColumns
Yes
Comma-separated list
One or more column addresses to search for ABAP object matches. At least one entry is required.
testCasePathColumn
No
String
Column address for the test case path.
searchPaths
No
Comma-separated list
Scopes the search to specific paths.
confidenceThreshold
No
Integer 0–100
Minimum confidence for a match.
Excel has no secrets.
xray
filePath
Yes
File path (.xlsx, .xlsm, or .xls)
Path to the Xray export file on the agent host.
sheetName
Yes
String
The worksheet name that contains the test case data.
testCaseIdColumn
Yes
String
Column address for the test case ID (for example A).
testCaseNameColumn
Yes
String
Column address for the test case name.
testStepsColumn
Yes
String
Column address for the JSON test-steps payload.
testCasePathColumn
No
String
Column address for the test case path.
searchPaths
No
Comma-separated list
Scopes the search to specific paths.
confidenceThreshold
No
Integer 0–100
Minimum confidence for a match.
Xray has no secrets.
ado
url
Yes
URL string
The Azure DevOps organization or collection URL (e.g. https://dev.azure.com/MyOrg).
project
Yes
String
The Azure DevOps project name.
timeout
No
Integer (seconds)
Per-repository request timeout.
searchPaths
No
Comma-separated list
Scopes the search to specific paths.
ado does not accept confidenceThreshold.
Secrets (entered interactively):
password
Yes
Azure DevOps Personal Access Token (PAT).
certify
project
Yes
String
The Certify project name.
connectionString
Yes
OLE DB connection string
Must include Provider=.... Must not embed credentials (user id, uid, password, pwd).
uidProp
No
String
Property name used when appending the username (default User ID).
pwdProp
No
String
Property name used when appending the password (default Password).
searchPaths
No
Comma-separated list
Scopes the search to specific paths.
confidenceThreshold
No
Integer 0–100
Minimum confidence for a match.
Secrets (entered interactively — optional):
username
No
Database user. Leave blank for Windows Integrated Authentication.
password
No
Database password. Leave blank when username is blank.
ssm
url
Yes
URL string
The Solution Manager OData base URL.
client
Yes
String
The sap-client query parameter (e.g. 100).
solution
Yes
String
Solution title as shown in Solution Manager.
branch
Yes
String
Branch title as shown in Solution Manager.
rfcDest
No
String
An existing [[rfc]].name for optional RFC enrichment.
searchPaths
No
Comma-separated list
Scopes the search to specific paths.
confidenceThreshold
No
Integer 0–100
Minimum confidence for a match.
Secrets (entered interactively):
username
Yes
Solution Manager user account name.
password
Yes
Solution Manager user account password.
alm
url
Yes
URL string
The OpenText ALM server URL (e.g. https://alm.example.com/qcbin).
domain
Yes
String
The OpenText ALM domain.
project
Yes
String
The OpenText ALM project name.
clientDirectory
Yes
Absolute path
Absolute customer folder containing OTAClient.dll and WebClient.dll (source for staging at testrepo set).
requirementType
No
String
Reserved for future requirements operations.
requirementAuthor
No
String
Reserved for future requirements operations.
searchPaths
No
Comma-separated list
Scopes the search to specific paths.
confidenceThreshold
No
Integer 0–100
Minimum confidence for a match.
Secrets (entered interactively — provide exactly one credential pair):
username
One of username+password or apikey+apisecret
OpenText ALM account username.
password
One of username+password or apikey+apisecret
OpenText ALM account password.
apikey
One of username+password or apikey+apisecret
OpenText ALM 15+ API key.
apisecret
One of username+password or apikey+apisecret
OpenText ALM 15+ API secret.
--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 username and password interactively (secrets are not accepted via --setting).
Examples for other types — each Test Tool Integrations page has a matching Command Prompt / PowerShell example:
Test a Test Repository Connection
slabapcli testrepo test
Runs a live connection test for a configured test repository adapter by dispatching a task to the ABAP Agent server.
--pipeline
-p
Yes
The pipeline name (must match a [[pipeline]].name value in config.toml).
--testrepo
—
Yes
The test repository name (must match a [[testrepo]].name value linked to this pipeline).
Example
If the connection test reports that the configured test repository was not available to the server (TESTREPO_NOT_FOUND / TestrepoNotFound), verify the expected [[testrepo]] entry and pipeline association in the active config.toml, then re-run the printed slabapcli testrepo test command. When this occurs after testrepo set, the configuration remains saved. See Configuration settings if a recent config edit is not yet reflected.
List Test Repositories
slabapcli testrepo list
Lists all test repository adapter entries defined in your config.toml file.
This command takes no parameters.
Example
Secret settings (username, password, apikey, apisecret, clientId, clientSecret) are always masked in the output.
Last updated
Was this helpful?