Events
Mar 17, 9 PM - Mar 21, 10 AM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register nowThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Azure DevOps Services
Using the custom fields allows storing the custom data against the test run and/or test result. There can be up to 100 custom fields defined for a single Azure DevOps project. Project administrator can manage (add/delete) the set of the custom fields.
Category | Requirements |
---|---|
Access levels | - At least Basic access, with permissions to view work items under the corresponding Area Path. - To add test plans and test suites, delete test artifacts, and define test configurations: Basic + Test Plans access. Or, one of the following Visual Studio subscriptions: - Enterprise - Test Professional - MSDN Platforms |
Permissions | - To add or modify test plans, test suites, test cases, or other test-based work item types: Edit work items in this node permission set to Allow under the corresponding Area Path. - To modify test plan properties such as build and test settings: Manage test plans permission set to Allow under the corresponding Area Path. - to create and delete test suites, add and remove test cases from test suites, change test configurations associated with test suites, and modify a test suite hierarchy (move a test suite): Manage test suites permission set to Allow under the corresponding Area Path. |
For more information, see Manual test access and permissions.
There are two ways to manage the custom fields - either via REST API or project administrator can do that through the Project settings while choosing Test management under Pipelines. On that page new custom field can be added by clicking on the + Add new button.
Choose + Add new to add a new custom field. Each custom field must have a name, type configured, and indicate what type of artifact it applies to.
The name of custom field cannot be longer than 50 characters (spaces, numbers, and special characters are not allowed) and must be unique in the project. The names are case insensitive, so you cannot have one custom field named "Test" and the other one named "test". Type can be one of the following:
The existing custom fields can either be edited (only name can be changed) or removed.
Note
After removing the custom field, you cannot use its name for about a day. The background process that is removing the deleted custom fields permanently is run ones a day.
You can store your custom data into the configured custom fields either as part of the test run/result creation or after the test run/result was created. Both can be done using REST API for now. In the future we will allow the custom data to be picked up from the test results file. To get the values stored in your custom fields for the existing test run/result, you must use the REST API. For the moment we do not display the custom fields and values stored in these on the Azure DevOps UI (we will be adding that ability in the future).
When you’re creating test run and/or result via REST API and want to store custom data to existing custom field, then the best option for you is to send the custom data as part of the test run and/or result creation. To create a test run call REST API Runs - Create and to create test result call REST API Results - Add.
When the test run and/or result is not created via REST API, but by other means, then you must first find the identification of the test run or result for which you want to set (or update) the custom data in the custom fields and then call REST API Runs - Update for the test run and REST API Results - Update for the test result.
To retrieve the custom data from the custom fields stored previously against the test run and/or result, you must first find the identification of the test run or result. Then you can call REST API Runs - Query for the test run and REST API Results - Get for the test result.
The custom data for the custom fields are sent or received in an array. Each item of that array contains two properties "fieldname" and "value" and you can see an example of that here. The value is object of the type that matches the type configured for the custom field. To understand the type of the custom field you may want to use REST API that provides array of the custom fields. For each field you can find there its ID, name, type and scope. You may also hardcode the type if you know what the type of the custom field of given name is.
Events
Mar 17, 9 PM - Mar 21, 10 AM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register nowTraining
Module
Run quality tests in your build pipeline by using Azure Pipelines - Training
Find out about automated testing that proves your code to be maintainable, understandable, and functioning without repetitive manual testing.
Certification
Microsoft Certified: Dynamics 365 Field Service Functional Consultant Associate - Certifications
Demonstrate how to configure a Microsoft Dynamics 365 for Field Service implementation to maximize tools and features available while managing a mobile work force.
Documentation
Run manual tests - Azure Test Plans
Learn about test tools to run manual tests with Azure Test Plans to make sure each of the deliverables meets your user's needs.
Test plans frequently asked questions - Azure Test Plans
Learn about frequently asked questions (FAQs) on test plans in Azure DevOps.
Navigate Test Plans - Azure Test Plans
Learn how to navigate Test Plans.