Familiarize yourself with the main key concepts of Thunders

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 '+'.

—> For more information about managing projects, check out this article: Add / Edit / Delete a Test Project

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.

You will only need to import your project requirement file or copy paste a user story and let Thunders write your test scenarios for you.

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.

—> For more information about managing Test Cases, check out these articles:

-Add / Edit / Delete a Test Case

-Run one or multiple Test Case(s) from the Test Cases list

-Execute a Test Case

Test files are like a library where you can find all the input/output files used in your test cases with the ability to download them or view the test case(s) they are linked to

—> For more information about managing Test assets, check out this article: Upload / Reference / Download / Edit / Delete a Test Asset

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.

—> For more information about managing Test Sets, check out this article: Test Sets - Add, Edit, Delete & Execute

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.

—> For more information about managing Test Runs, check out these articles:

-View a Test Run Report

-Run one or multiple Test Case(s) from the Test Cases list

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 through APIs.

—> For more information about managing Environment, check out this article: Add / Edit / Delete an Environment

When you run your test scenario, Thunders presents a catalog of specialized Personas, each with a unique personality and capabilities, allowing you to evaluate your project from multiple perspectives and receive detailed reports on various aspects.

-> For more information on managing personas, check out this article: Meet our personas

→ Also discover how to customize your accessibility expert persona