Why TestIT Doesn't Show Test Cases in Test Plan

Problems with displaying test cases from a library in a test plan in TestIT usually occur due to incorrect configuration of relationships between test cases and plans, or due to access permission restrictions. The most common reasons include the lack of proper binding of test cases to a project, incorrectly configured visibility filters, or problems with data synchronization between the library and the test plan.

Table of Contents

• Main Causes of the Problem
• Step-by-Step Solution to the Problem
• Additional Checks
• Tips for Beginners
• When to Contact Support

Main Causes of the Problem

Several factors can cause a situation where test cases from the library don’t appear in the test plan:

1. Lack of project binding - Test cases must be bound to the same project as the test plan. If test cases are created in another project or don’t have the proper binding, they won’t be visible in the plan.

2. Access permission restrictions - Ensure you have the necessary permissions to view and add test cases to test plans. Sometimes even creating test cases doesn’t automatically give you the right to add them to plans.

3. Incorrect tag filters - Test plans may have tag filters that exclude visibility of certain test cases. Check if there are tag restrictions applied in the test plan.

4. Synchronization issues - The system may require additional synchronization between the test library and the test plan, especially when working with large volumes of data.

5. Test case status - Some test plans may only display test cases with a specific status (e.g., “Ready” or “Active”), which affects their visibility.

Step-by-Step Solution to the Problem

Follow these steps to diagnose and solve the problem:

1. Check Project Binding

Ensure that test cases are bound to the correct project:

• Go to the test library
• Select the problematic test case
• Check the “Project” field in the test case details
• Make sure the project matches your test plan’s project

2. Check Access Permissions

Check your permissions in the system:

• Go to your profile settings
• Navigate to the “Access Rights” section
• Ensure you have rights to:
  • View test cases
  • Manage test plans
  • Add test cases to test plans

3. Configure Filters in the Test Plan

Check the filter settings in the test plan:

• Open the test plan
• Find the “Filters” or “Display Settings” section
• Ensure there are no restrictions on:
  • Test case statuses
  • Priorities
  • Tags
  • Automation

4. Manual Synchronization

Try to manually synchronize data:

• Find the “Refresh” or “Synchronize” button in the interface
• In some versions of TestIT, there may be a separate library synchronization command
• Wait for the synchronization process to complete fully

5. Check Test Case Status

Ensure that test cases have the correct status:

• In the test library, check the status of each test case
• Test plans may only display test cases with “Ready”, “Active”, or similar status
• If necessary, change the status of test cases manually

---

Important: As stated in the official TestIT documentation, to bind an automated test to a test case, special actions must be performed for the test case to be considered automated during test plan execution.

Additional Checks

If the main steps didn’t help, perform the following checks:

Test Plan Configuration Check

1. Test plan hierarchy - Ensure you’re working with the correct hierarchy level. Sometimes test cases may only be visible at certain nesting levels.

2. Execution configuration - Check the test execution configuration settings. Some configurations may restrict visibility of certain types of tests.

System Version Check

1. System currency - Ensure you’re using the latest version of TestIT. Sometimes display issues are fixed in updates.

2. Version-specific bugs - Check for known issues in your system version through documentation or knowledge base.

Alternative Addition Methods

1. Addition via import - Try importing test cases into the test plan via a CSV file or other supported format.

2. Batch addition - If there are many test cases, try adding them in batches rather than one by one.

---

Expert Tip: As test management specialists note, in systems like TestIT, it’s important to understand the difference between a test plan and a test case. A test plan and a test case are different entities, and their proper interaction requires attention to configuration details.

Tips for Beginners

To prevent similar problems in the future:

1. Create test cases in the correct project - Always check which project you’re creating test cases in.

2. Use standard tags - Develop and adhere to a tagging system for better organization and filtering.

3. Regularly update statuses - Maintain current test case statuses for their proper display in plans.

4. Document processes - Keep notes on how you configure test plans and bind test cases.

5. Use templates - Create templates for frequently repeated test plan setup operations.

---

Important for beginners: Don’t hesitate to ask for help from more experienced colleagues or the system’s technical support. Problems with displaying test cases are a common situation, and there’s always a solution.

When to Contact Support

If all the above steps didn’t help, contact TestIT technical support, providing:

1. Screenshots of the problem (as you did)
2. The version of the TestIT system
3. A description of the steps taken to resolve the problem
4. Error logs, if available
5. Information about your account’s access rights

Such problems often require intervention from system administrators or developers, especially if they’re related to database configuration or system limitations.

Conclusion

The problem with displaying test cases from a library in a TestIT test plan is solvable. The main recommendations are:

1. Always check that test cases are bound to the correct project
2. Ensure you have sufficient access permissions for all necessary operations
3. Carefully configure filters in test plans
4. Regularly synchronize data between system components
5. Monitor the current status of test cases

For beginners, it’s important to remember that proper organization of test cases and test plans is key to effective testing. Don’t be afraid to experiment with settings and document your actions for future reference.

Sources

1. Automating Test Cases | Test IT
2. Test Plan vs Test Case: Core Differences | BrowserStack
3. Managing a Library of Test Cases with Quality Center
4. Navigate Test Plans - Azure Test Plans | Microsoft Learn