G

Integration

Available for both SaaS and On-Premise.

Targetprocess can integrate with your existing development tools to create a central hub for collaboration and management across your enterprise. Get rid of information islands and standardize your process across your entire organization.

see Full list of integrations

How to import Test Cases and Test Steps from a CSV file

It is possible to bulk add Test Cases to Targetprocess using the Import from CSV files feature. Since detailed Test Steps were introduced in Targetprocess, the import action of Test Cases is now performed in a different way. Currently there are two options available.

Place steps in Description field in Test Cases

The first option uses the Description field of Test Cases. This field allows to store Steps and Success details as well as other relevant data. Download the CSV file template, fill it with your values and run the import. At this point there is no need to deal with individual Test Step entities at all.

1) Create a CSV file with Test Cases list having three mandatory columns containing:

  • Project ID or Name
  • Name for Test Cases. Single line text strings.
  • Description for Test Cases. HTML markup is supported.

Test Cases List CSV file

Test Plan column is not mandatory. However should an imported Test Case be attached to any Test Plan, fill the column with an ID of the Test Plan.

2) Go to Settings → Import.

3) Select Test Case from "Select type of entities to import" dropdown menu.

4) Click "Choose file" button to upload the .csv file created in step 1 and click "Next" button.

5) Match columns from .csv file with corresponding fields and click "Next".

Test Cases CSV file columns mapping

6) Test Cases import is completed, click "Next" once again to look through the log.

Imported Test Case

Insert detailed Test Steps for Test Cases

The second option is to break down Steps and Success details of the Test Case into separate Test Steps entities. This method requires two steps to complete the import instead of one. First, create Test Cases through importing them from a list (download CSV file template), and then import detailed Test Steps for each Test Case from another list (download CSV file template).

Step 1. Test Cases Pre-Import

1) Create a CSV file having two mandatory columns containing:

  • Project ID / Name
  • Name for Test Cases. Single line text strings.

Test Cases list CSV file

Test Plan column is not mandatory. However should an imported Test Case be attached to any Test Plan, fill the column with an ID of the Test Plan.

2) Go to Settings → Import.

3) Select Test Case from "Select type of entities to import" dropdown menu.

4) Click "Choose file" button to upload the .csv file and click "Next" button.

5) Match columns from .csv file with corresponding fields and click "Next".

Test Cases CSV file columns mapping

6) Test Cases import is completed, click "Next" once again to look through the log.

Here's how the imported Test Case looks. Detailed steps are still missing, let's add them!

Imported Test Case

Step 2. Detailed Test Steps Import

1) Create a CSV file with Test Steps having four mandatory columns containing:

  • Project ID / Name
  • Test Case Name or ID of Test Case considered as parent to Test Step.
  • Description of Test Step. HTML markup is supported.
  • Results of Test Step. HTML markup is supported.

Test Steps CSV file

2) Go to Settings → Import.

3) Select Test Step from "Select type of entities to import" dropdown menu.

4) Click "Choose file" button to upload .csv file and click "Next" button.

5) Match columns from .csv file with corresponding fields and click "Next".

Test Steps CSV file columns mapping

6) Test Steps import is completed, click "Next" once again to look through the log.

Here"s how the imported Test Case with Test Steps looks:

Imported Test Steps

You cannot control Run Order (i.e. Test Steps sequence) within an Import action so far. All new Test Steps are always added to the end of the Steps list for a relevant Test Case. You can further rearrange them in Targetprocess manually, using drag'n'drop action.

Import Test Cases and detailed Test Steps from single CSV file

It is possible to use a common CSV file for both Test Cases and Test Steps. Download CSV file template, fill it with your values and run the import.

Common CSV file for Test Cases and Test Steps

1) Go to Settings → Import.

2) Select [Dynamic entity type definition] from "Select type of entities to import" dropdown menu.

3) Click "Choose file" button to upload .csv file and click "Next" button.

4) Select TestCase as Type to Import.

5) Match columns from .csv file with corresponding fields and click "Next" several times.

Test Case columns mapping

6) Select TestStep as Type to Import.

7) Match columns from .csv file with corresponding Targetprocess entity fields and click "Next" several times.

teststepimportmapping

As a result, a Test Case with two Test Steps is created and attached to the specified Test Plan.

Test Step export and import are compatible, which means that you can edit your exported Test Cases and Test Steps outside Targetprocess and then import them back.

Import Test Cases into Test Plans, User Stories and other assignable entities

It is possible to import Test Cases into existing Test Plans. It is also possible to import Test Cases for assignable entities (including User Stories, Features, Bugs). The key principle here is that test cases are not linked to work items directly. Instead, every work item may have its associated test plan which keeps collection of test cases. And new test cases must be imported to this collection rather than to the work item itself.

Entity Test Plan

  1. In Targetprocess, create a test plan for an entity or open existing test plan
  2. Copy its numeric ID
  3. In your CSV file with list of test cases, add Test Plan column
  4. For each test case paste the numeric ID of target parent test plan
  5. Save your CSV file
  6. When doing import, map Test Plan column properly
  7. Imported test cases become linked to proper test plans

We will illustrate this flow for User Story test cases. The same actions can be applied to Features, Bugs and other assignable items as well.

Create Test Plan for an entity

In User Story detailed view, open Tests tab. Create new Test Plan for the User Story.

userstory-testplan-create

New Test Plan for the User Story is created. Initially it is empty.

userstory-testplan-new-empty

Find numeric ID of Test Plan of an entity

From detailed view for a User Story, open detailed view for Test Plan. You will find its numeric ID there.

userstory-testplan-open-detailed-view

userstory-testplan-id

Prepare CSV file with list of Test Cases

Copy this numeric ID and paste it into "Test Plan" column of Test Cases list. Save your CSV file.

import-testcases-testplan

Import CSV file with list of Test Cases

Perform import of test cases file using wizard as shown below (Settings → Import)import-test-case-step1

 

import-testcases-step3

import-testcases-log

Imported test cases appear in Tests tab for user story and in its test plan as well.

userstory-testcases-imported

It is no longer possible to map User Story column during import of Test Cases. This won't work since v3.7.0 when Entity Test Plan feature has been introduced.

Import Test Case into multiple Test Plans

In the CSV file, the Test Plan column for every test case can contain only a single numeric ID of target parent test plan.

However, it is possible to update existing test cases and add links to test plans. It is done one addition operation per row. Within CSV file you pass rows that contains numeric ID of existing test case, link (numeric ID or name) to its parent Project and link (numeric ID) to the test plan you would like to include this test case to.

For this purpose please create in your CSV file and map three columns:

  • Project → Project
  • Test Case ID → ID
  • Test Plan → Test Plan

testcase-import-testplan-update

test-case-parent-test-plan-id

Newly added links do not overwrite existing connections between test cases and test plans.

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.

Try for free

Account url: *.tpondemand.com
How many people would be using Targetprocess?
  • Myself
  • 2–20
  • 21–100
  • 101–1000
  • 1000+
By clicking Continue you agree to our Terms of service and Privacy policy