Helper Scripts

TestIntel provides standalone helper scripts that work independently — no TestIntel installation required. Just Python 3.11+.

Quick Start: Import Your Existing Tests

If your team already has automated tests, you can populate TestIntel's inventory in under a minute. Here's the workflow:

Step 1: Download the scanner

Go to Help → Helper Scripts in TestIntel, or download directly: scan_tests.py

Step 2: Scan your repo

python scan_tests.py --path C:\repos\my-project

The scanner finds all test files (BDD, pytest, Robot Framework, JUnit, Playwright/Cypress) and exports them to test-scan.csv.

You'll see a summary like:

Scan complete:
  BDD/Gherkin:           12 scenarios from 4 files
  pytest:                45 tests from 8 files
  Playwright/Cypress:     6 tests from 2 files

Total: 63 tests exported to test-scan.csv

Step 3: Upload to TestIntel

1. Open TestIntel and select your project from the dropdown

1. Go to the Inventory tab

1. Click Upload Results (or use the Chat to say "import these tests")

1. Upload the test-scan.csv file

Your tests are now tracked in TestIntel's inventory with their names, types, tags, and source file paths.

Step 4: Start generating new tests

With your existing tests visible, TestIntel's AI can identify coverage gaps and generate tests that complement what you already have — no duplicates.

Script Reference

Test Scanner — Import Existing Tests

Already have tests in your repo? The test scanner finds them and exports a CSV you can upload to TestIntel's inventory.

Supported frameworks:

• BDD/Gherkin (.feature files)
• Robot Framework (.robot files)
• pytest (test_*.py, *_test.py)
• JUnit/TestNG (*Test.java, *Tests.java)
• Playwright/Cypress (*.spec.ts, *.spec.js, *.test.ts, *.test.js)

Download: scan_tests.py

Usage:

# Scan entire repo
python scan_tests.py --path /path/to/repo

# Only scan BDD and pytest
python scan_tests.py --path /path/to/repo --frameworks bdd,pytest

# Custom output file
python scan_tests.py --path /path/to/repo --output my-tests.csv

# Exclude directories
python scan_tests.py --path /path/to/repo --exclude node_modules,.venv

Output: A CSV file with columns: name, type, priority, tags, steps, automation_status, source_file

Upload the CSV to TestIntel via the Inventory tab's import feature.

Model Smoke Test — Verify an AI Model

Quickly confirm an AI model works with TestIntel before making it a default or

adding it to the verified-models table.

Unlike the other helper scripts, this one runs from within a TestIntel install

(it uses TestIntel's own provider code so the checks match real behavior).

Location: scripts/smoke_test_model.py

Prerequisites:

• TestIntel installed (pip install -e .)
• The provider API key set as an environment variable (ANTHROPIC_API_KEY,

OPENAI_API_KEY, or AWS credentials for Bedrock)

What it checks (in order):

1. Model resolves — the model id exists on the provider's models endpoint

(Anthropic/OpenAI; skipped for Bedrock, which validates at call time)

1. Basic chat — a non-streaming request returns text

1. Streaming — the streaming path yields at least one chunk

1. Structured generation — a test-case prompt returns output that resembles

test cases

Usage:

# Test the model from your current config.yaml
python scripts/smoke_test_model.py

# Override provider and/or model without editing config.yaml
python scripts/smoke_test_model.py --provider anthropic --model claude-sonnet-4-6
python scripts/smoke_test_model.py --provider openai --model gpt-4o

Exit code: 0 if all applicable checks pass, 1 otherwise — so it can be

used in CI or a pre-release check.

When a model passes, add it to the verified-models table in

docs/configuration-reference.md.

Jira Export — Export Tickets to CSV

Export Jira tickets to CSV for use as requirements input to TestIntel.

Download: jira_export.py

Prerequisites:

• pip install httpx
• Jira API token from https://id.atlassian.com/manage-profile/security/api-tokens

Usage:

# Set credentials
export JIRA_EMAIL=you@company.com
export JIRA_API_TOKEN=your-token

# Export a project
python jira_export.py --url https://yourorg.atlassian.net --project HR

# Export specific tickets
python jira_export.py --url https://yourorg.atlassian.net --tickets HR-1,HR-6,HR-8

# Export with JQL
python jira_export.py --url https://yourorg.atlassian.net --jql "project = HR AND type = Bug"

Output: A CSV file with columns: Issue Key, Summary, Issue Type, Priority, Status, Labels, Description, Acceptance Criteria, Assignee, Reporter, Created, Updated