Entity Test Plan

Entity Test Plan is available starting with the Targetprocess v3.7.0 release.

For every entity mentioned below it’s possible to create a related test plan with a set of test cases and test plans within the entity:

  • Epic
  • Feature
  • User Story
  • Task
  • Bug
  • Request
  • Build
  • Iteration
  • Team Iteration
  • Release

Entity Test Plan

For example, you can first create a user story test plan and later, when you’d like to test the whole feature, including this user story, you can create a feature test plan and include this and other user story test plans into a feature test plan with just a few clicks. Later, when it’s time to test the whole release, we can create a release test plan and automatically include all the feature test plans to it.

Create an Entity Test Plan

A test plan can be created on a Tests tab on an entity view. It can be created as empty or automatically include related entities’ test plans.

Create an Entity Test Plan

When a related test plan is created, it inherits an entity name, and the words ‘Test Plan’ are added to the end of the name. The name can be changed to a different one if necessary. A related test plan is the same as a usual test plan and behaves in exactly the same way. The only difference is that it is linked to an entity, as a user story, feature, bug, etc.

If the No Test Plan option is selected, an empty related test plan is created. Now it is possible to create new or link existing test cases and test plans to this test plan. All the added test cases and test plans will appear on the Test Plan tab of an entity view.

As soon as a test plan is created for an entity a new Test Plan section will become visible in the right section of an entity view, so that you can quickly overview test plan details. To open a test plan view, click a test plan details icon in this section.

Entity Test Plan. Image 3

Here we can see how many test plan runs are created for a user story test plan and what the last run results are. From this panel you can create a new test plan run or continue executing the existing one if it is the only test plan run in progress.

A test plan which relates to an entity has an entity icon next to an entity name.

Entity Test Plan. Image 4

In the related entity field it is possible to see the exact entity a test plan relates to:

Entity Test Plan. Image 5

You can unlink this test plan from an entity if needed by simply clearing this field. You can also link an entity to an existing test plan if you select it in this field.

When you create a test plan and select an option to link related entities’ test plans, then test plans of the mentioned related entities (tasks and bugs, or features for example), if they exist, will be automatically linked to the created test plan. You will still be able to modify, i.e create or link test cases and test plans, or unlink the automatically linked test plans, if you need to do so.

In the example below you can see a Release Test Plan which includes all the related User Stories Test Plans:

Entity Test Plan. Image 6

Note: There is no automatic synchronization of an entity test plan with its related entities test plans. For example, you’ve created a Release Test Plan and selected to link all the User Stories and Bugs Test Plans to it. If new user story is added to a release after the release test plan creation, the user story test plan will not be automatically linked to the release test plan. However, you can manually link it if required.

When selecting an option to link related outbound or inbound entities test plans, then all the test plans which exist for outbound or inbound relations for this entity, will be linked to a created test plan.

User Story Test Plan Migration

For user stories which had test cases before the release 3.7.0 there will be an option to convert a set of related test cases to a test plan, i.e create a related test case to a user story test plan and link all the existing test cases to it.

User Story Test Plan Migration

This will allow you to execute a user story test plan multiple times and reuse the same test cases to test different user stories.

It is still possible to work with test cases without migration. However, a lot of possibilities, which new functionality brings, will be missed till migration.

Bug with Feature and User Story relation

When executing a feature or user story test plan and a bug is found and linked to a test plan run, then this bug will automatically be linked to a related feature or user story.

It will happen only when you create a test plan run from a feature or user story test plan. When you create a test plan run from a user story or feature child test plan, bugs will not be linked automatically, as this test plan is considered as an independent test plan and can be used in many different entity test plans.

Test Units for Entities

Similar to Test Plans, you can now select test units to be shown on entity cards on views. For example, you can add Test Cases, Run Results and Last Run Date units to see how many test cases are in a related test plan, view the latest run results, and determine when it was last executed:

Test Units for Entities

Test Cases and Test Plans on Views

It is possible to select entities as lanes and show the related test cases and test plans as cards. Let’s imagine there are Iterations with a related Test Plans. When we select iterations as lanes and test cases and test plans as cards, then we will see an Iteration as a lane and all the first level test cases and test plans, which belong to an iteration test plan as cards. This allows us to track test plans and test cases coverage.

Test Cases and Test Plans on Views

For non-migrated user stories you will see all the linked directly test cases.

Import Test Cases

It is possible to insert test cases into test plan for every entity. Prepare CSV file with list of test cases and perform import.

Still have a question?

We're here to help! Just contact our friendly support team

Find out more about our APIs, Plugins, Mashups and custom extensions. Join our community of passionate users and even discuss directly with our developers.