run-tests

Included with Lifetime

$97 forever

Execute AL test codeunits. Use al-runner for fast pure-logic tests (no BC required). Use bc-test for full integration tests against a running BC instance.

Code Review

What this skill does


# /run-tests — Execute AL Tests

## Two Test Runners

| Tool | When to use | BC required? | Speed |
|------|------------|-------------|-------|
| `al-runner` | Pure-logic unit tests (in-memory tables, no pages/HTTP/events) | No | Milliseconds |
| `bc-test` | Full integration tests against a running BC instance | Yes | Seconds–minutes |

## al-runner (preferred for unit tests)

**Full AI agent guide:**
```bash
al-runner --guide
```

**Basic usage:**
```bash
# Run all tests
al-runner ./src ./test

# With symbol packages
al-runner --packages .alpackages ./src ./test

# With stubs for unsupported dependencies
al-runner --packages .alpackages --stubs ./stubs ./src ./test

# Run a single test procedure
al-runner --run TestMyProcedure ./src ./test

# With coverage report
al-runner --coverage ./src ./test

# Machine-readable JSON output
al-runner --output-json ./src ./test

# JUnit XML for CI
al-runner --output-junit results.xml ./src ./test
```

**Exit codes:**
| Code | Meaning |
|------|---------|
| 0 | All tests passed |
| 1 | Real assertion failures |
| 2 | Runner limitations only (compilation gaps, missing mocks — not real failures) |
| 3 | AL compilation error |

Use exit code 2 to distinguish runner gaps from real failures in CI.

**What al-runner supports:** in-memory tables, CRUD, filters, cross-codeunit calls, interfaces, asserterror, JSON types, BLOB/InStream/OutStream, RecordRef/FieldRef, IsolatedStorage, TextBuilder, and more. See `al-runner --guide` for the full list.

**What al-runner does NOT support:** Pages, Reports, XMLports, HTTP calls, event subscribers. Inject these via AL interfaces or use `--stubs`.

## bc-test (full BC integration)

Expects `bc-test` on PATH (from bc-linux or bc-tools).

```bash
bc-test --help
```

Use when tests require BC's service tier, events, UI flows, or features not supported by al-runner.

## Behavior

1. Determine which runner is appropriate for the test type
2. Parse `$ARGUMENTS` and pass through to the selected tool
3. If there's an active task folder (`.dev/<task-slug>/`), capture output to `.dev/<task-slug>/test-results.txt`

## Handling Results

- **All passing (al-runner exit 0):** Report pass count. Note "Tests green."
- **Exit 2 (al-runner):** Runner limitations only. Not a real failure — add stubs or use bc-test for the blocked tests.
- **Real failures:** List each failed test with codeunit, method name, and error message. Offer to analyze and suggest fixes.
- **No tests found:** Check that test codeunits use `Subtype = Test` and mark procedures with `[Test]`.

Files: 1

Size: 2.7 KB

Complexity: 6/100

Category: Code Review

Source: https://github.com/stefanmaron/claude-configs/tree/main/profile-al-development/skills/run-tests

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts