Make the most out of your experience and check
articles about TestCaseLab functionality

Suites are essential for organizing your test case repository into logical categories. With up to 4 levels of subsuites, you can structure your test cases to align with your project’s needs.

Learn what is a Suite here.

‍

1. Create a Suite

• Navigate to the Test Cases page.
• Click the ‘+’ button in the Suites section to add a new Suite.

‍

2. Restructure Suites

Use drag-and-drop in the Suites section to rearrange Suites or restructure the hierarchy of your repository.

‍

3. Access Test Cases in a Suite

Click on a Suite in the Suites section to view all test cases assigned to it.

‍

4. Rename a Suite

Rename a Suite using one of these methods:

• Click the three-dot menu in the Suites section and select ‘Rename’.

• Click on the Suite title in the Test Cases List and edit the name in-line.

‍

5. Duplicate a Suite

To duplicate a Suite:

• Use the three-dot menu in the Suites section and select ‘Duplicate.’
• Both the Suite and its associated test cases will be copied.

‍

6. Delete a Suite

To permanently delete a Suite:

• Use the three-dot menu in the Suites section and select ‘Delete.’
• Both the Suite and its test cases will be removed.

Note: This action is irreversible.

‍

7. Create a Subsuite

Use the three-dot menu in the Suites section to create a subsuite under an existing Suite.

‍

8. Customize the Suites Section

• Collapse or expand Suites for better navigation.
• Hide the Suites section when you need to focus on the Test Cases List.

‍

What’s Next?

Managing Suites effectively ensures your test case repository stays organized and easy to navigate. For further assistance, check related guides or contact support. We’re happy to help!

‍

A Suite in TestCaseLab acts as a category or folder to organize test cases within a project. Suites provide a logical structure to your test case repository, making it easier to manage, navigate, and execute tests efficiently. 

• Categorize test cases to align with your project’s structure or testing strategy.
• Quickly locate and manage test cases by grouping them logically.
• Handle large projects effectively with multiple levels of grouping for test cases.

‍

Key Features of a Suite

1. Purpose

• Organize test cases into logical groups, such as by features, modules, or testing phases.
• Simplify locating and managing test cases within a structured framework.

‍

2. Hierarchical Organization

• Create up to 4 levels of subsuites within a project.
• Mirror your system’s structure or testing process by organizing test cases hierarchically.

‍

Working with Suites and Test Cases

1. Grouping Test Cases

Suites group test cases in the Test Cases List, allowing you to quickly locate test cases assigned to a specific Suite.

‍

2. Filters

Apply filters to view only the test cases from selected Suites, making it easier to focus on specific areas of testing.

‍

3. Visibility Options

Collapse, expand, or hide the Suites Section to customize your workspace and improve navigation.

Learn more about Suite management here.

‍

What’s Next?

For additional assistance, explore related guides or contact support.

‍

A Test Case in TestCaseLab is a detailed and structured description of a testing scenario. It outlines the steps, conditions, and expected outcomes required to verify a specific feature or functionality of your system. Test Cases form the foundation of the testing process, ensuring consistency, thoroughness, and quality in your testing efforts.

‍

Key Features of a Test Case

1. Purpose

Defines the scope of a single test, describing:

• What to test: The feature or functionality under examination.
• How to test it: The steps and conditions needed for execution.
• The expected result: The desired outcome after execution.

‍

2. Components of a Test Case

Each Test Case in TestCaseLab includes the following details:

• Title: A concise name for the test case.
• Priority: Indicates importance (e.g., High, Medium, Low).
• Type: Categorization of the test case (customizable in Project Settings).
• Preconditions: Requirements or setups needed before starting the test.
• Steps: Detailed actions to perform the test.some text
  • Write steps using text mode or step table mode.
  • Include up to two attachments per step for clarity.
• Expected Results: The desired outcome after completing the steps.
• Tags: Labels to help organize and filter test cases.
• Custom Fields: Extra fields for project-specific details (customizable in Project Settings).
• Attachments: Additional files or images to support the test case.

Learn more about Test Case management here.

‍

3. Flexibility in Editing

Modify all fields of a test case in Test Case Details via edit-in-place functionality or dive deep into thorough editing of a test case via the Edit Case Form.

‍

4. Reusability

Test Cases are reused across multiple Test Plans and Test Runs, ensuring efficiency and consistency.

‍

5. Organization

• Group Test Cases into Suites for better management.
• Use filters, tags, and custom fields to locate and organize test cases easily.

Learn more about Suites here.

‍

What's Next?

Test Cases are essential for ensuring the quality and reliability of your system. For further assistance, explore related articles or contact support—we’re here to help!

‍

Customizing your test case template ensures your project workflow matches your team's unique needs. Follow these steps to configure test case types, tags, and custom fields.

Learn what is a Test Case here.

‍

1. Access Project Settings

• Go to the project where you want to customize the test case template.
• Navigate to Project Settings to begin customization.

Note: Only Project Administrators can access Project Settings.

‍

2. Manage Test Case Types

Types allow you to filter and organize test cases, making it easier to locate specific cases.

• Open the Test Case Types page in Project Settings.
• Use the predefined list of types or add your own based on your project needs (e.g., Approved, Pending Approval, Draft).
• Set a default type for new test cases. 

Note: The Type assigned by default to a Test Case can be updated individually in the Test Case Details.

‍

3. Manage Test Case Tags

Tags help filter the test case list, enabling quick and easy navigation.

• Go to Project Settings > Test Case Tags to manage your tags:
  • Rename tags to keep them relevant.
  • Delete tags that are no longer needed.

Note 1: Creating tags is available while editing a test case by typing into the ‘Tags’ field.

Note 2: Use the test case list filter to filter by tag, or simply click on a tag to apply the filter directly.

‍

4. Add Custom Fields

Expand your Test Case Template by adding extra fields (text areas and dropdowns).

• Navigate to Custom Fields in Project Settings.
• Create up to 5 custom fields for your project:
  • Text Fields: Add free-text information.
  • Dropdown Fields: Define options for categorization.
• Control visibility of fields on project pages:
  • Show or hide fields on the Test Cases and Test Plan pages.
  • Show or hide fields on the Test Run page.

Examples: Specify details such as devices, versions, browsers, and environments using custom fields.

Note 1: You can filter test cases by dropdown values while working with the test cases list.

Note 2: Custom fields are always visible on the Edit Test Case page for universal editing.

‍

What’s Next?

Customizing your test case template simplifies test management and enhances team collaboration. If you need additional guidance, check out our related articles or contact support. We’re happy to assist!

‍

With TestCaseLab It is possible to run tests and report bugs instantly to your favorite bug-tracking tool. If you're looking for a test case management tool that integrates with GitHub, try TestCaseLab. 

The instructions below will help you set up the integration with the GitHub tool.

‍

1. Generate API token

• First of all, you should log in to your GitHub account.‍

Note: Make sure that you have an active project on your GitHub account to integrate it with your TestCaseLab project. 

• Navigate to your GitHub account and click on your ‘Profile’ icon. Choose the  ‘Settings’ option from the menu.

• On the ‘Profile Settings’ page find ‘Developer Settings’, and click on it.

• Click on the ‘Personal access tokens’ tab and choose the ‘Tokens (classic)’ option. 

• Click on 'Generate new token' and choose the ‘Generate new token (classic)’ option.

• Fill in the ‘Note’ field, and mark up all required checkboxes. Click on the 'Generate token' button.

• Copy your Access token to the clipboard. 

‍

2. Set up Connection

• After that, you need to navigate to your TestCaseLab Company Account, click on ‘Project Settings’ in the sidebar and go to the ‘Integrations’ tab.
• Choose GitHub from the list of Bug tracking tools. 

• Paste your Personal access token, and click on the 'Test connection' button.
• Choose your Project from the list, and confirm the action.
• As long as there are no issues and the Connection is established, you can proceed with Integration and save the changes.

A 'Connected' notification means your connection has been established without any issues, and you are able to report your defects directly to GitHub. 

‍

What’s Next?

If you have any questions, our support team is here to assist you!

‍

The TestCaseLab tool lets you run tests and report bugs right away to your favorite bug-tracking system. TestCaseLab integrates with the Mantis bug-tracking tool, so you can manage defects easily.  

The following instructions will guide you through setting up the Mantis integration.

‍

1. Generate API token

• As a first step you should log in to your Mantis account. 
• Navigate to your Mantis account and click on your ‘Profile’ icon. Choose the  ‘My account’ option from the menu.

• From the ‘My account’ tab go to the ‘API tokens’ tab.

• Fill in the ‘Token name’ field, and click on the 'Create API token' button. Copy your API token to the clipboard. 

‍

2. Set up Connection

• After that, you need to navigate to your TestCaseLab Company Account, click on the ‘Project Settings’ in the sidebar and go to the ‘Integrations’ tab.‍
• ‍Choose the Mantis tool from the list of Bug tracking tools. 

• Paste your API Key to the ‘API Key’ field. 
• Copy your Mantis URL, and paste it to the ‘URL’ field. Example: https://YOURNAME.mantishub.io/
• Click on the 'Test connection' button, then choose your Project from the dropdown menu and confirm the action.

You can report your defects directly to Mantis from TestCaseLab once you receive the 'Connected' notification.

‍

What’s Next?

If you have any questions, our support team is here to assist you!

‍

In software development, TestCaseLab simplifies and optimizes QA processes. Your favorite bug-tracking tool can be used to execute tests and report bugs immediately. You are welcome to try TestCaseLab if you are looking for a test management tool that integrates with Asana. 

To learn how to set Asana test case management tool, follow the instructions below.

‍

1. Generate API token

• First of all, you should log in to your Asana testing tool account to integrate TestCaseLab with Asana. 
• Click on your ‘Profile’ icon and choose the ‘My Settings’ option.

• On the ‘Settings’ page navigate to the ‘Apps’ tab and click on the ‘Manage Developers Apps’ option.

• Click on the 'Create new token' button.

• Fill in the ‘Name’ field, click on the ‘I agree to the API terms and conditions’ checkbox. After that, please confirm the action by clicking on the 'Create token' button.

• Copy your token by clicking on the 'Copy' button and close the modal window by clicking on the 'Done' button. 

‍

2. Set up Connection

• After that, you need to navigate to your TestCaseLab Company Account, click on the ‘Project Settings’ in the sidebar and go to the ‘Integrations’ tab. 
• Choose the Asana test case management tool from the list of Bug tracking tools. 

• Paste your Personal access token, and click on the 'Test connection' button.
• Choose your Workspace and Project from the list, and confirm the action.

The 'Connected' notification indicates that your connection has been established without any issues. From TestCaseLab, you can report your defects directly to Asana. 

‍

What’s Next?

If you have any questions, our support team is here to assist you!

‍

By using the TestCaseLab tool, you can easily run tests and report bugs. The Youtrack bug-tracking tool is easily integrated with TestCaseLab.

Here is a quick guide to configure the integration.

‍

1. Generate API token

• As a first step, you should be logged in to your Youtrack test management account.
• Click on your Profile icon in the header and then go to the ‘Profile’ page by clicking on the respective point from the menu.

• Navigate to the ‘Account Security’ tab.

• Click on the 'New token' button. 

• In the token transition screen enter a Token name, choose a scope (you can choose from suggested by Youtrack), and click on the 'Create' button. 

• Click on the 'Copy token' button.

‍

2. Set up Connection

• After that, you need to navigate to your TestCaseLab Company Account, click on the Project Settings via sidebar and go to the ‘Integrations’ tab.
• Choose Youtrack from the list of Bug tracking tools. 

• Paste your Personal access token to the ‘Personal access token’ field.
• Navigate to your Youtrack account and copy your URL. Example: https://YOURNAME.youtrack.cloud
• ‍After that paste your Youtrack URL to the ‘URL’ field, and click on the 'Test connection' button.
• Choose your Youtrack project from the projects list and confirm the action. 

If you see a 'Connected' notification it means that your connection has been established without any issues and defects can be reported directly from TestCaseLab  to Youtrack.

‍

What’s Next?

If you have any questions, our support team is here to assist you!

‍

It is easy to run tests and report bugs using the TestCaseLab test management system. 

Set up integration with the Pivotal tracker using a short manual below.

‍

1. Generate API  token

• To get started, log into your Pivotal account.
• Сlick on your name in the header and choose the ‘Profile’’ option from the menu.

• Scroll down the Profile page to the ‘Api token’ tab.

• Click on the 'Create new token' button, and copy the created token to your clipboard.

‍

2. Set up Connection

• After that, you need to navigate to your TestCaseLab Company Account, click on the ‘Project Settings' and go to the ‘Integrations’ tab.
• Choose the Pivotal tool from the list of Bug tracking tools. 
• Paste your API token to the ‘API key’ field, and click on the 'Test connection' button.
• Chose a project from the projects list and confirm the action.

Upon receiving a ‘Connected’ notification, your connection has been established without any issues. It means that defects can be reported directly to Pivotal.

‍

What’s Next?

If you have any questions, our support team is here to assist you!

‍