In Thunder Code, there are six key concepts:

A test project is the highest-level container that groups related test artifacts together and helps organize testing efforts across different features or modules.

Test projects also hold context and knowledge bases, which are valuable for better interpreting instructions.

You can create a new Test Project easily by going to "Test Projects" and clicking '+'.

A test project is specific to a technology (web app, mobile app, or API).

An environment represents a specific deployment context where tests are executed, such as development, staging, or production. Each environment can have its own URL and secrets.

Managing different environments is crucial for ensuring that tests are executed under the right conditions and produce reliable results.

You can create environments through the web interface (clicking Add) or APIs.

A test plan is a strategic document that outlines the testing approach, objectives, scope, and resources needed for testing a specific feature or module. It serves as a roadmap for the testing process and helps ensure comprehensive test coverage.

The Test Plan feature will be available in the second half of 2025.

A test case is a detailed specification of test inputs, execution conditions, and expected results designed to verify specific functionality or requirements. It includes step-by-step instructions for test execution and validation criteria.

A test set is a collection of related test cases grouped together to test a specific feature, component, environment, or functionality. Test sets help organize and structure test cases logically, making it easier to execute and manage related tests as a unit.

A test run represents the actual execution of test cases or test suites in a specific environment. It captures the test results, including pass/fail status, execution time, and any defects found during testing. Test runs provide valuable data for tracking testing progress and quality metrics.

Test Runs are created only when you queue a test to run asynchronously (through CI/CD, API, or from the web application)—not while building and debugging a test.