The same is true for the field’s Type, which cannot be changed either.Īll previously mentioned properties apply globally, i.e. The system name must be unique and cannot be changed after the field was created. The system name is used as the actual database field name, for XML files and internal data structures. The System Name is the name TestRail uses internally to represent the field’s value. The description is usually displayed below the field in TestRail. The label is the display name of the field, whereas the description is an optional explanation of what the field does. The Label and Description properties define how the custom field is displayed in TestRail’s user interface. The User field is a dropdown box that contains all user names of the TestRail installation.Ī custom field has several properties and options that must be considered when you add new fields. This can be both a public internet address or the address of a web page in a local intranet. The URL (Link) field can be used to store a web address. You can specify if a Text field should support Markdown formatting or just plain text. This field is similar to the Text field.Ī Text field is a multi-line text box that allows users to enter text of arbitrary length. The String field is a single-line text box that allows users to enter arbitrary text. This field can only be used with test results. It enables users to assign a test status to each step of the related test case. The Step Results field is the matching type for the Steps field. This field can only be used with test cases. This field can be combined with the Step Results field for ticking off individual steps in the test result dialog. The Steps field allows users to enter test case steps in a structured way. Multi-select fields use the same configuration format as Dropdown fields (i.e. The Milestone field is a dropdown box that contains all milestones of the current project as items.Ī multi-select field can be used to store multiple, predefined values (e.g. If a user tries to enter a value that is not a number, a validation error is raised and the user is asked to enter a valid number instead. Integer fields can be used to enter numbers. You can change the order, add new options or delete options without affecting existing values because of this. That is why you are asked to enter your values as number/option pairs when you configure a Dropdown custom field. TestRail stores the selected value internally as a number. The user can then select one of the presented values. The edit box for this field includes a handy calendar control to make it easier to pick a date.Ī Dropdown field can be used to present multiple choices. So if you have a field that has only two possible values, checkboxes are commonly used for that.Ī Date field can be used to record a date value. TypeĪ checkbox can be used to record boolean values (true/false or yes/no). The following custom field types are currently supported by TestRail. For example, a Text field allows users to enter arbitrary text, whereas a Date field only allows date values as a valid value. The type of a custom field specifies what kind of information the field can store and how it’s rendered. TestRail supports several custom field types. Custom fields for test results can be used to record additional information when test results are entered (for example, on the Add Test Result dialog). Custom fields for test cases allow you to add additional details to your test cases. TestRail currently supports custom fields for two entities, namely for test cases and test results. You can manage custom fields in the administration area under Administration > Customizations in TestRail.
0 Comments
Leave a Reply. |