Script Test

1. Overview

The Script Test feature in AgileTest works like a testing checklist, allowing QA teams to define a series of checkpoints that need to be verified during testing projects.

Instead of detailed step-by-step instructions with specific expected results, Script Test suits quick verifications. It works best for validations without complex setup and extensive documentation.

Here is the comparison table between Script Test and Classic Test

	Classic Test	Script Test
How it work as	Structured test cases with predefined steps and expected results	A checklist for verifying key points without predefined steps
Preparation	Preconditions, test steps, sample data, expected results	Short checklist items
Setup Process	Create Test Cases Group into Test Plans Create Test Executions when executing	Create reusable checklists Add Test Runs when executing
Documentation	Test Execution Results can be tracked in Milestone, Dashboard, and Reports.	Test Run Results can be tracked in Milestone and Dashboard.
When to choose	New projects or complex features When step-by-step clarity is required When detailed evidence/reporting is required by stakeholders When long-term documentation and traceability are priorities	Tight deadlines where speed is critical Existing or stable features that need quick regression checks When testers are already familiar with the product Quick high-level coverage before writing detailed test cases

While Classic Test suits structured processes and detailed reports, Script Test is ideal for

Fast verification (smoke test, sanity check, quick regression).
Minimal setup and preparation with checklists are enough.
Frequently re-validate stable or familiar features.
Tracking in Milestones and Dashboard is sufficient, without requiring formal Reports.

→ Instead of choosing only one, many QA teams combine both approaches. Teams use Script Test (Checklist) to quickly list and cover all main scenarios at a high level. Then, teams create Classic Test Cases for critical, complex, or high-risk scenarios that require detailed step-by-step documentation.

To find Script Test in AgileTest, go to the Script Test section on the left-hand side menu bar.

In AgileTest, each Script Test is also a Jira work item.

Check out this video below of how testers can utilize our Scripts feature to maximize testing workflow

2. Locate Script Tests

You can find test scripts in 2 areas: AgileTest Script Test Section and Jira Sprint Board.

2.1 Find Script Tests In AgileTest

On the left menu sidebar, navigate to the Classic Test section → Choose Script Test.

2.2 Find Script Tests In Jira

On your Jira Sprint board, you can find these script tests as Jira work items.

3. Create New Script Tests

Inside the Script Test section, click on the “+ Test Script” button.

Fill in the script test details.

Summary: A clear and concise title that reflects what the checklist test is verifying.
Description (Optional): Additional context if needed, such as the scope of validation, environment details, or any important notes to help testers understand the purpose of this Script Test.

Click on the “Create” button to finish.

How to Create Multiple Script Tests Without Repeating the Process

Follow the same steps used to create the first script tests. In the 3rd step, select “Create another” instead of clicking “Create”.

This keeps the dialog open after the script test is created, allowing you to continue creating and editing additional script tests without reopening the dialog each time.

Explore more about AgileTest Script Tests

Manage Script Test

Understand Script Test Components

Should you need any assistance or further AgileTest inquiries, contact our 24/7 Support Desk!