qatech configure

Configures the CLI with your QA.tech API key. By default the key is saved to .qatech/config.json in the current directory so each project can have its own key. Use --global to write to ~/.qatech/config.json as a fallback.

Usage

qatech configure [options]

Options

Flag	Short	Description
`--api-key <key>`	`-k`	Set the API key (saves to local config by default)
`--global`	`-g`	Save to `~/.qatech/config.json` instead of project-local
`--show`	`-s`	Show the active configuration and where each value comes from
`--help`	`-h`	Show command help

Examples

# Interactive setup (saves locally)
qatech configure

# Non-interactive - set the project-local key
qatech configure -k <your-api-key>

# Set the global fallback key
qatech configure -k <your-api-key> --global

# Inspect what the CLI is using
qatech configure --show

Resolution order

The resolved key is the first match from:

--api-key flag on the running command
QATECH_API_KEY environment variable
.qatech/config.json in the current directory (project-local)
~/.qatech/config.json (global fallback)

qatech configure --show reports the active key (masked), the source it came from, and both config file paths so you can see exactly which file you’re editing.

Security

The config file stores your raw API key - treat it like any other credential. Add .qatech/ to your .gitignore if you want to keep project-local keys out of source control.

Get your API key from app.qa.tech → Settings → Integrations → API.

CLI Overview qatech test-cases

Get Started

Core Concepts

Configuration

Best Practices

Test Features

Integrations

Applications

CLI

Usage

Options

Examples

Resolution order

Security

​Usage

​Options

​Examples

​Resolution order

​Security

Usage

Options

Examples

Resolution order

Security