Blog

The AI Assistant helps you create and review QA artifacts inside your project using natural language.

In the current version, you can use the AI Assistant to:

• Create Test Cases from scratch.
• Create Requirements from scratch.
• Create Test Cases based on existing Requirements.
• Ask questions about existing Test Cases and Requirements.

The AI Assistant works only with the project you currently have open.

1. Open the AI Assistant

To open the AI Assistant:

• Open a project.
• Click the AI Assistant button.
• Enter your request in the chat panel.

You can describe what you want to create or ask a question about existing Test Cases and Requirements.

Note: The AI Assistant uses the current project context only.

2. Create Test Cases from Scratch

You can ask the AI Assistant to create new Test Cases by describing the feature, flow, or scenario you want to cover.

For example, you can provide:

• Feature name.
• User flow.
• Preconditions.
• Expected behavior.
• Edge cases.
• Priority or type, if needed.

The AI Assistant will prepare Test Cases based on your request and show a preview before creating them.

Review the preview carefully, then confirm the action if everything looks correct.

3. Create Requirements from Scratch

You can ask the AI Assistant to create Requirements by describing the product functionality or business need.

For example, you can provide:

• Feature description.
• User goal.
• Business rule.
• Expected behavior.
• Constraints or acceptance conditions.

The AI Assistant will prepare Requirements based on your request and show them for review before saving.

Note: You should review generated Requirements before confirming creation.

4. Create Test Cases from Requirements

You can generate Test Cases from existing Requirements.

To do this:

• Ask the AI Assistant to create Test Cases from one or more Requirements.
• Specify which Requirement or group of Requirements should be used.
• Add any extra testing focus if needed, such as edge cases, negative scenarios, or regression coverage.
• Review the generated Test Cases.
• Confirm creation.

The generated Test Cases will be based on the selected Requirements.

Note: This helps keep test coverage connected to product scope.

5. Ask Questions About Test Cases

You can ask the AI Assistant for information about existing Test Cases.

For example, you can ask it to:

• Find Test Cases related to a feature.
• Summarize Test Cases for a specific area.
• Identify Test Cases with specific tags, types, or priorities.
• Explain what a group of Test Cases covers.

The AI Assistant will return information based on the Test Cases available in the current project.

6. Ask Questions About Requirements

You can also ask the AI Assistant for information about Requirements.

For example, you can ask it to:

• Find Requirements by title, status, type, or tag.
• Summarize Requirements for a feature.
• Identify Requirements without related Test Cases.
• Explain what a Requirement covers.

Use this to quickly understand product scope and test coverage.

7. Review Before Saving

When the AI Assistant creates Test Cases or Requirements, review the generated content before confirming.

Check that:

• Titles are clear.
• Steps and expected results are accurate.
• Requirements match the intended business logic.
• Generated Test Cases cover the right scenarios.

Note: The AI Assistant helps speed up drafting, but final review stays with the user.

What’s Next?

Use the AI Assistant to draft Test Cases and Requirements faster, or to get quick information about existing project coverage. For additional help, check related guides or contact support—we’re here to help!

‍

The Requirements page helps your team define, organize, and track product requirements inside a project.

Requirements can be linked to Test Cases, giving your team clear traceability from product scope to test coverage, execution, and defects.

1. Open the Requirements Page

To work with requirements:

• Open your project.
• Go to the Requirements page.
• Use the page to create requirements, organize them by category, and link them to Test Cases.

The Requirements page includes:

• Categories tree
• Requirements list
• Requirement details panel
• Search
• Sorting
• Filters
• Bulk Actions

2. Create Requirement Categories

Categories help organize requirements into logical groups.

To create a category:

• Go to the Categories section.
• Click the ‘+’ button.
• Enter the category title.
• Save the category.

You can create nested categories up to 4 levels deep.

You can also:

• Rename categories.
• Create subcategories.
• Rearrange categories with drag and drop.
• Delete categories.

Note: Deleting a category does not delete the requirements inside it. Requirements are moved to the parent category or to ‘Requirements without Category’.

3. Create a Requirement

To create a requirement:

• Select a category.
• Click ‘+ Requirement.’
• Enter the requirement title.
• Click on the requirement to see Requirement Details.
• In the Requirement Details set:
  
  • Requirement type
  • Requirement status
  • Add a description, tags, assignees, or attachments if needed.

Available requirement types include:

• Epic
• Feature
• User Story
• Use Case
• Functional Requirement
• Non-Functional Requirement
• Business Requirement

Note: ‘User Story’ is the default requirement type.

4. Manage Requirement Details

Click a requirement row to open the Requirement Details panel.

From the details panel, you can view and update:

• Title
• Category
• Type
• Description
• Status
• Tags
• Assignees
• Attachments
• Metadata

The details panel also includes tabs for:

• Details
• Test Cases
• Defects
• Audit Log

Note: Requirement descriptions support plain text and markdown.

5. Link Requirements to Test Cases

Use the Test Cases tab to link requirements with related Test Cases.

To link Test Cases:

• Open a requirement.
• Go to the Test Cases tab.
• Search for Test Cases by title or key.
• Select the Test Cases you want to link.

Linked Test Cases are synchronized both ways. If you link a Test Case from the requirement, the requirement also appears in the Test Case’s Related Requirements field.

Note: Up to 10 Test Cases can be linked to one requirement.

6. Track Defects from Linked Test Cases

The Defects tab shows defects connected to test results from linked Test Cases.

You can view:

• Last tested date
• Defect count
• Test Run
• Test Result status
• External defect link
• Timestamp

Use this tab to understand whether a requirement has known issues based on related test execution.

7. Use Requirement Filters and Search

Use filters to narrow down the Requirements list.

Available filters include:

• Assignee
• Category
• Status
• Type
• Tags
• Orphaned requirements

You can also search by:

• Requirement title
• Requirement key
• Requirement details

Note: An orphaned requirement is a requirement that has no linked Test Cases.

8. Use Bulk Actions

Bulk Actions help update multiple requirements at once.

Available Bulk Actions include:

• Edit
• Duplicate
• Delete
• Assign
• Status update

Bulk Actions follow the same behavior and confirmation patterns as Test Cases.

9. Import and Export Requirements

You can import requirements from CSV, including:

• Categories
• Requirement Title
• Requirement Description
• Status
• Type
• Tags

You can also export requirements to CSV.

10. View Requirement History

The Audit Log tab shows changes made to the requirement.

Tracked changes include:

• Field updates
• Status changes
• Tag changes
• Attachment changes
• Test Case linking and unlinking
• Requirement deletion and restoration

What’s Next?

Use Requirements to connect product scope with test coverage and execution results. For additional help, check related guides or contact support—we’re here to help!

‍

Project Milestones help you organize Test Runs around release goals, testing windows, or QA deadlines. Use milestones to group related Test Runs, track progress, and quickly identify missed deadlines.

Milestones are optional. You can continue using Test Runs without milestones if your workflow does not require deadline tracking.

1. Create a Project Milestone

To create a milestone, you have to be a Project Administrator. Please follow the instructions:

• Open your project.
• Go to the Milestones page.
• Click the ‘+ Milestone’ button.
• Fill out the milestone details:
  • Title: Enter a clear milestone name.
  • Description: Add optional context, links, or release notes.
  • Start Date: Set the beginning of the testing window, if needed.
  • Due Date: Set the deadline for the milestone, if needed.
  • Test Runs: Select the Test Runs that should belong to the milestone. You'll be able to add Test Runs later.
• Save the milestone.

Note: Project Milestones are created at the project level and do not apply across multiple projects.

2. Assign Test Runs to a Milestone

You can assign Test Runs to a milestone from:

• The Milestone details page.
• Test Run settings or Test Run details.

A milestone can include multiple Test Runs. Each Test Run can be assigned to one milestone at a time.

3. Understand Due Date Logic

If a milestone has a Due Date, assigned Test Runs inherit that due date.

When a Test Run inherits a due date from a milestone:

• The due date is shown on the Test Run.
• The due date is read-only on the Test Run.
• The milestone is shown as the source of the due date.

If a Test Run is not assigned to a milestone, you can set a manual due date directly on the Test Run.

Note: If no milestone is assigned and no manual due date is set, the Test Run has no due date by default.

4. Track Missed Deadlines

A Test Run is considered missed when:

• The due date has passed.
• The Test Run is not Completed.

Missed deadlines are highlighted in the Test Runs list and on the Test Run details page.

If the due date comes from a milestone, the Test Run will show the milestone as the source.

5. View Milestone Progress

The Milestones list helps you monitor testing progress across time-bound goals.

The list includes:

• Title
• Start Date
• Due Date
• Test Run status summary
• Completion progress
• Test Runs count

Use filters to focus on milestones by status, date range, or missed Test Runs.

6. Open Milestone Details

The Milestone details page gives a full overview of milestone progress.

You can view:

• Milestone title and status.
• Start and due dates.
• Total Test Runs list.

From the Test Runs section, you can open a Test Run, edit it, or remove it from the milestone.

7. Manage Milestones

Project Administrators can:

• Edit milestone details.
• Archive milestones.
• Restore archived milestones.
• Delete milestones.
• Assign or remove Test Runs.

Other project roles have read-only access to milestones.

What’s Next?

Use Project Milestones to organize testing around releases, deadlines, or regression cycles. For additional help, check related guides or contact support—we’re here to help!

‍

If you're looking to generate test cases using AI and send them directly to your TestCaseLab project, Treeify makes the process simple and effective. With Treeify’s AI-assisted workflows, you can create test scenarios in minutes — and with our integration, export them to your TestCaseLab workspace in just a few clicks.

This guide will walk you through how to connect Treeify to your TestCaseLab account and start exporting test cases right away.

‍

What You'll Need

To export AI-generated test cases from Treeify to TestCaseLab, you’ll need:

• API Token
• Company ID

These three values are required to enable secure and accurate test case transfers. Follow the steps below to find them.

‍

1. Get Your API Token

Ask your Company Admin in TestCaseLab to generate an API token.

1. Go to Company Settings > Company Profile.
2. Find the API Tokens section.
3. Create and copy the token.

API tokens allow you to integrate TestCaseLab with external tools like Treeify securely. Only Company Admins have access to manage them.

‍

2. Find Your Company ID

You’ll use the API token with a tool like Postman to retrieve your Company ID.

Get Company ID

• Send a GET request to:https://app.testcaselab.com/api/v2/companies
• Include your API Token in the Authorization header:Authorization: Bearer YOUR_API_TOKEN

Example Response:

[

 {

   "id": 123,

   "name": "Your Company Name",

   "subdomain": "yourcompany"

 }

]

• Copy the id value — that’s your Company ID.

‍

3. Connect Treeify and Start Generating Test Cases

Once you have all the data — API Token, Company ID — you are ready to start in Treeify.

• Sign in to your Treeify personal account (note: company-wide accounts are not yet supported).
• Generate test cases via Treeify
• Navigate to the TestCaseLab export integration option.

• Input:
  • Your API Token
  • Your Company ID
• Confirm and export them directly to your selected TestCaseLab project.

‍

How to work with Treeify? Learn

here.

‍

Good to Know

‍

You can report any issues directly via the “Report a Bug” feature in Treeify. Since the tool is still in beta, your feedback will help the team enhance the user experience.

Smarter Testing Starts Here

This integration bridges the power of Treeify’s AI-assisted test generation with the structure and collaboration features of TestCaseLab. Whether you’re refining test coverage or scaling your QA team’s workflow, this setup helps you do it faster and more intelligently.

Let your QA flow better — with AI and TestCaseLab.

‍

TestCaseLab offers three types of reports to analyze and share Test Run results. Reports can be accessed from the Test Run page and shared externally with stakeholders, even if they don’t have access to the Company Account.

Test Run reports also include the Test Run description and Due Date when it is available.

Learn more about Test Runs here.

‍

1. General Report

Provides a high-level summary of the Test Run results.

Includes:

• Number of Test Cases Executed: Total count of test cases run.
• Number of Defects Reported: Issues identified during the Test Run.
• Test Run Assignees: List of users assigned to the Test Run.
• Pie Chart: Visual statistics based on test case result statuses (e.g., Passed, Failed, Blocked).
• Activity per User: Tracks contributions by each team member.
• List of Test Cases with Results: Detailed table showing the status of all test cases.

‍

2. Failed Test Cases and Defects Report

Focuses on problem areas by highlighting failed test cases and associated defects.

Includes:

• Pie Chart: Visual statistics on the number of failed test cases.
• Number of Defects: Total count of defects reported during the Test Run.
• Reporters List: Identifies users who reported defects.
• Failed Test Cases List: Table of test cases that failed.
• Defects List: Detailed information about reported defects.

‍

3. Comparison of Test Runs

Allows comparison of results across multiple Test Runs.

How to Generate:

• Select up to 4 Test Runs for comparison.
• Click the ‘Show Report’ button to generate the comparison.

Use Case: Ideal for identifying trends and analyzing progress, especially when comparing Test Runs based on the same Test Plan.

‍

What’s Next?

Generate the report type that aligns with your needs to gain insights into testing activities and outcomes. For additional assistance, check related guides or contact support—we’re here to help!

‍

Running tests ensures thorough execution and accurate tracking of your system's quality. Use this guide to effectively execute test cases, log results, and analyze outcomes.

Learn what is a Test Run here.

‍

1. Run Tests Using the Checklist

• Use the Test Cases List in the Test Run for quick execution:
  • Quick Pass: Click the ‘Quick Pass’ button to mark a test case as Passed.‍
  • Change Status: Use the dropdown menu to set the test case status to:‍
    • Not Tested (default).‍
    • Passed.‍
    • Failed.‍
    • Blocked

• For Failed or Blocked Tests:
  • A modal window appears when setting a test case to Failed or Blocked.
  • In the modal, you can:
    • Add comments for additional context.
    • Attach files such as screenshots or logs.
    • Report a Bug:
      • Automatically via integrated tools
      • Manually by adding a bug link.

Read more about Integrations here.

‍

2. Run Tests in the Test Case Detail

• Open Test Case Details to execute tests step-by-step:
  • Set individual step results as you work through the test case.
  • If any step is marked as Failed or Blocked, the system automatically updates the entire test case status accordingly.
  • Add comments, attachments, or report bugs directly within the details view

• Use the ‘Next’ button to move to the next Not Tested test case.

‍

3. Completing the Test Run

Once all test cases are executed, the Test Run status updates to Completed.

‍

4. View Test Run Reports

• After completion, a detailed Test Run Report is generated, including:
  • A summary of results (e.g., passed, failed, blocked cases).
  • Logs for each test case.
• Use the report to:
  • Analyze results.
  • Compare outcomes across up to 4 Test Runs to track progress and identify trends.

Read more about Reports here.

‍

What’s Next?

Running tests in TestCaseLab ensures accurate tracking and documentation of your testing process. For further assistance, check related guides or contact support—we’re here to help!

‍

Create a Test Run

Creating a Test Run helps organize and execute a specific set of test cases to meet your testing objectives. Follow this guide to set up a Test Run efficiently.

Learn what is a Test Run here.

‍

1. Create from the Test Plan’s Page

• Navigate to the Test Plan’s page and select the Test Plan you want to use.
• Click the ‘Create Test Run’ button.
• The Test Run will automatically include the test cases from the selected Test Plan, arranged in the same order defined in the plan’s Checklist.

2. Create from the Test Runs Page

• Go to the Test Runs page.
• Click the ‘+ Test Run’ button to open the creation form.
• Fill out the following details:
  • Title: Enter a unique name for the Test Run.
  • Description: Add optional context, such as scope, environment, release, or testing notes.
  • Test Plans: Select one or more Test Plans to base the Test Run on.
  • Milestone: Assign the Test Run to a Project Milestone, if needed.
  • Due Date: Set a manual due date if the Test Run is not assigned to a milestone.
  • Assignees: Choose the users responsible for executing the Test Run.

Note 1: Skip the ‘Test Plans’ field if you prefer to manually add test cases.

Note 2: If the Tes Run is assigned to a milestone with a due date, the Test Run inherits the milestone due date and the due date becomes read-only.

3. Manually Include Test Cases

If you skipped the Test Plans field during creation:

• Open the Test Run’s inner page.
• Click ‘Edit Run’ to access the test case selection interface.
• Use the checkboxes to select the test cases you want to include in the Test Run.

‍

4. Start Running

Once the Test Run is prepared and all desired test cases are included, start the execution process.

Learn more about running Test Runs here.

‍

Manage a Test Run

Managing a Test Run ensures your testing process stays organized and adaptable to your needs. Follow this guide to work efficiently with Test Runs.

‍

1. Test Run View Modes

Test cases in a Test Run can be displayed in two modes:

• Grouped-by-Suite View Mode:
  • Default view, grouping test cases by Suites.
  • Sorting is inherited from the Test Cases page and can only be updated by Project Administrators.

• Checklist View Mode:
  • Displays a flat list of test cases.
  • Test cases can be rearranged using drag&drop by any Project Member.
  • Ideal for customizing the order for convenient testing workflows

‍

2. Rearranging Test Cases

• Checklist View Mode:
  • Use drag-and-drop to reorder test cases for your preferred testing sequence.

Note: Changes in Checklist View Mode do not affect the order in the Grouped-by-Suite View Mode.

• Test Runs Created from Test Plans:
  • If the Test Run is based on a Test Plan, the test case order from the Test Plan is applied.

Note: Any changes made in the Test Run will not affect the Test Plan’s original order.

‍

3. Edit a Test Run

Use the ‘Edit Run’ modal to update Test Run details:

• Title: Modify the Test Run name.
• Assignees: Add or change the testers assigned to the Test Run.
• Include/Exclude Test Cases: Adjust the list of test cases in the Test Run.

Note: Newly added test cases in Checklist View Mode will appear at the bottom of the list.

You can also update the Test Run description from the ‘Edit Run’ modal.

Use the description to add helpful execution context, such as:

• Scope of testing.
• Environment.
• Release version.
• Special notes.
• Links to related documentation.

Note: The description supports plain text and clickable links.

‍

What’s Next?

Managing Test Runs effectively ensures smooth execution and adaptability for testing needs. For additional help, check related guides or contact support—we’re here to help!

‍

Test Runs are one-time executions of test cases designed to validate functionality and quality.

Managing Test Runs helps streamline test execution and keep track of testing progress and results. Use the following guide to effectively organize and manage your Test Runs.

Learn what is a Test Run here.

‍

1. Create a Test Run

• Go to the Test Runs page.
• Click the ‘+ Test Run’ button to add a new Test Run.

Note: Test Runs can be created either based on pre-created Test Plans or by adding test cases directly into an empty Test Run.

Learn more about creating a Test Run here.

2. Sort Test Runs

Sort Test Runs by Name for better organization.

‍

3. Filter Test Runs

Apply filters to focus on specific Test Runs based on:

• Status: Filter by Not Started, In Progress, or Completed Test Runs.‍
• Assigned to You: View Test Runs where you are the assigned tester.‍
• Cases Within Runs Assigned to You: Focus on specific test cases assigned to you within a Test Run.

4. View Test Run Due Dates

The Test Runs list can show additional context for each Test Run.

Use the list to view:

• Due Date: Shows the Test Run deadline, if one is set.

If a Test Run misses its due date, the due date is highlighted.

Note: A Test Run is missed when its due date has passed and the Test Run is not Completed.

If the due date is inherited from a milestone, the Test Run will show the milestone as the source.

5. Manage Test Runs

• Duplicate: Create a copy of an existing Test Run for reuse.‍
• Archive and Restore:‍
  • Archive Test Runs to temporarily remove them from active use.
  • Restore archived Test Runs when needed.‍
• Delete: Permanently delete Test Runs that are no longer required.

Note: Deleted Test Runs cannot be restored.

‍

6. Export Test Run Reports

Generate and export reports from completed Test Runs in the following formats:

• CSV
• PDF
• Online View

Learn more about reports here.

‍

7. Switch Test Runs List View Modes

• Line View: A standard list format for Test Runs.

• Grid View: Displays pie charts for visual tracking of progress and completion status.

8. Use Bulk Actions

Bulk Actions help you manage multiple Test Runs at once.

To use Bulk Actions:

• Click 'Bulk Actions' to see checkboxes next to each Test Run
• Select one or more Test Runs using the checkboxes in the list.
• The ‘Bulk Actions’ menu will appear.
• Choose the action you need.

Available Bulk Actions for Test Runs:

• Archive
• Unarchive
• Delete
• Export to CSV
• Export to PDF
• Duplicate
• Assign Users to Test Run

Note: You can select up to 1000 Test Runs in one bulk action.

‍

What’s Next?

Efficiently managing Test Runs ensures a smooth testing workflow and accurate reporting of results. For additional help, check related guides or contact support—we’re happy to assist!

‍

A Test Run is a one-time execution of a set of test cases within a project. It enables testers to verify the functionality and quality of a system by following predefined test cases and logging the results.

• Manage testing activities effectively and monitor progress.
• Verify that all planned test cases are executed.
• Systematically document results for reporting and analysis.

‍

Key Features of a Test Run

1. Purpose

Test Runs are used to execute test cases and record test results such as 

• Pass, 
• Fail, 
• Block.

‍

2. Creation

Test Runs can be created in two ways:

• From a Pre-Created Test Plan: Quickly generate a Test Run using a prepared template of test cases.
• Manual Test Run: Select and add test cases individually to create a custom Test Run.

‍

3. Execution

Once a Test Run is started, you can:

• Execute each test case in the list.
• Record outcomes and provide additional details like comments, attachments, and defects if necessary.

Learn about running tests here.

‍

4. Reporting

• Upon completing a Test Run, the system generates an automated Test Run Report that includes:
  • A summary of results (e.g., passed, failed, blocked cases).
  • Detailed logs for each test case.
• Reports can be exported in CSV, PDF, and viewed online.

Learn about Reports here.

‍

5. One-Time Execution

A Test Run is executed once. If retesting is required, a new Test Run should be created.

‍

What's Next?

For further assistance, check related guides or contact support—we’re happy to help!

‍