Since version 1.2, TFS IP started to work on Orchestrator 2012 RC. In version 1.4, eight activities are added to support the test management.

Add Test Case Result

Input parameters
  • Test Run ID: identifier of the TestRun object. It can be retrieved using "Get Test Runs" activity.
  • Test Run Title: optional, you may use either ID or title (if it's unique) to identify the TestRun object. If both are provided, ID will be preferred. If multiple TestRun objects exist for the given title, the one with largest ID will be used.
  • Build Number: optional,
  • Test Case ID: ID of the test case associated with the result. Note that the test case must have been added to a test suite in a test plan in the team project.
  • Owner: the display name of owner, note it is usually full name in the form of "Firstname Lastname" instead of DOMAIN\alias.
  • Error Message: optional, error message associated with the result.
  • Test Outcome: Microsoft.TeamFoundation.TestManagement.Client.TestOutcome object to indicate the outcome of the test case result.
  • Date Completed: optional,
  • Date Started: optional,
  • Attachment: optional, file to be attached to the test case result.

This activity has no published data.

Create Test Run

Input parameters
  • Project: the name of the team project.
  • Test Plan ID: identifier of the test plan where the TestRun object should be resided in. It can be retrieved using "Get Test Plans" activity.
  • Test Plan Name: you may use either ID or name to identify the TestPlan object. If both are provided, ID will be used. If multiple plans can be found with the same name, the first one will be used.
  • Is Automated: if the test run is automated or manual.
  • Test Run Title: the title of the test run. Normally it is the test suite name or some combination of test suite name, build number and other information.
  • Build Number: which build does this test run against.
  • List of Test Suites: comma separated test suite IDs, the activity will recursively add all test cases to the test run.
  • List of Test Cases: common separated test case IDs. Note at least one test case should be added to the TestRun object when it's created, so either this or "List of Test Suites" needs to be empty.
  • Owner: the display name of owner, note it is usually full name in the form of "Firstname Lastname" instead of DOMAIN\alias.
  • Build Directory: optional,
  • Build Flavor: optional, Debug or Release, etc.
  • Build Platform: optional, x86 or x64, etc.
  • Date Completed: optional,
  • Date Started: optional,

Output
  • Test Run ID: identifier of the newly created TestRun object.

Get Shelveset

This activity queries the source repository to retrieve the list of files/directories being changed in a shelveset.

Input parameters
  • Shelveset Name: name of the shelveset, leave it empty for querying all shelveset of a user, in this case the Owner should be provided.
  • Owner: name of the owner of the sheleveset in the form of DOMAIN\alias. Note that at least one of two inputs should be non-empty. If both are specified, the intention is to find one shelveset and retrieve the changed files.

Output

If only one input is provided, a list of shelveset will be pushed with the following information:
  • Comment:
  • Creation Date:
  • Display Name: the display name of the shelveset.
  • Shelveset Name: the name of the shelveset.
  • Owner: the display name of the shelveset owner.

If both inputs are provided, a list of changed items in a single shelveset will be published with the following information:
  • Number of Objects: number of changed items.
  • Item Type: indicated if the changed item is a file or a directory.
  • File Name: file name of the changed item.
  • Change Type: type of the change, i.e. Add, Edit, Rename, Delete, Merge, etc.
  • Item Folder: folder of the item in the source repository.

Get Test Configurations

Input parameters
  • Project: the name of the team project.
  • Query: optional, work item query for refining the output, e.g. "Select * from TestConfiguration"

Output
  • Number of Objects: number of configurations being published.
  • ID: ID of the test configuration.
  • Area Path:
  • State: Microsoft.TeamFoundation.TestManagement.Client.TestConfigurationState, i.e. "Active" or "Inactive".
  • Description:
  • Test Configuration Name:

Get Test Plan

Input parameters
  • Project: the name of the team project.
  • Query: optional, work item query for refining the output, e.g. "Select * from TestPlan"

Output
  • Number of Objects: number of test plans being published
  • Test Plan ID:
  • Test Plan Name:
  • Description:
  • Owner:
  • Area Path:
  • State: Microsoft.TeamFoundation.TestManagement.Client.TestPlanState, i.e. "Active" or "Inactive".
  • Start Date:
  • End Date:
  • Iteration: the iteration to which this test plan belongs.

Get Test Runs

Input parameters
  • Project: the name of the team project.
  • Query: optional, work item query for refining the output, e.g. "Select * from TestRun"

Output
  • Number of Objects: number of TestRun object being published.
  • Test Run ID:
  • Test Plan ID:
  • State: Microsoft.TeamFoundation.TestManagement.Client.TestRunState object, i.e. "NotStarted", "InProgress", "Completed", etc.
  • Title:
  • Owner:
  • Is Automated:
  • Date Completed:
  • Date Started:
  • Build Number:
  • Build Flavor:
  • Build Platform:
  • Comment:
  • Error Message:
  • Iteration: the number of times that this test run has been executed.
  • Last Updated:
  • Last Updated By:
  • Total Tests: total number of tests in the test run. Note this number as well as the below could be empty if the statistics has not been updated.
  • Completed Tests:
  • Failed Tests:
  • Inconclusive Tests:
  • In Progress Tests:
  • Passed Tests:
  • Pending Tests:

Get Test Suites

Input parameters
  • Project: the name of the team project.
  • Query: optional, work item query for refining the output, e.g. "Select * from TestSuite"

Output
  • Number of Objects: the number of TestSuite object being published.
  • Test Suite ID:
  • Description:
  • Test Suite Title:
  • Test Suite State: Microsoft.TeamFoundation.TestManagement.Client.TestSuiteState object, i.e. "InPlanning", "InProgress", or "Completed".
  • Test Plan ID:
  • Test Plan Name:
  • State: (duplicated as Test Suite State. To be fixed)
  • Parent Test Suite ID: ID of the parent test suite if this test suite is not at the root level

Last edited Apr 19, 2012 at 11:43 PM by Yao, version 1

Comments

No comments yet.