The index (starting at 1) of the row where TestRail should start looking for test cases in the CSV file. Generally, the comma will be the correct option.
Standard CSV (short for Comma Separated Values) uses a Comma (,) but some sheets may be configured differently based on user preferences, how the file was created, or other factors. The text character used to indicate where information for the next cell should start. Excel/Windows commonly uses Windows-1252 (Latin) for CSV files whereas most other tools (including Google Sheets) prefer the Unicode-compatible UTF-8 encoding. By default, will select a blank value, which will add all defined sections as top-level, or they will be added to a generic “Test Cases” section if one is not defined in the CSV. Sections defined on your test cases in the imported CSV file will be added as sub-sections under this section. The base section or folder you would like to add your test cases to.
#Excel import xml with preset columns download#
You can download an example of a CSV formatted for the Test Case (Text) template below, as well as a template for your own test cases. This means all of the relevant steps and expected results for your test cases will be in their own single cells, and when imported, will populate their own large text fields. When using Test Case (Text) template, your import file should use the standard one row format – meaning all of the contents for a single test case in your CSV will be on one single row. Format your CSV depending on what test case template you’re usingĭepending on the template you are using for your test cases in TestRail, you may need to format your import CSV differently. You can learn more about Custom Fields in TestRail here, and find out more about Separated Test Steps here. You may not always need to specify this level of detail for every test in your test suite, but specifying separated steps can give you a lot more visibility and traceability because you can add individual test result statuses, and add links to specific defects, requirements, or other external entities for each step using the Defect/Reference integrations, and re-use steps across multiple test cases where applicable. The Test Case (Text) template allows for you to describe the steps testers should take to test a given case more fluidly, while the Test Case (Steps) template allows you to delineate individual Steps along with the Expected Result for each step. The other two default templates, Test Case (Text) and Test Case (Steps), both provide you with areas to specify Preconditions, Test Steps, and Expected Results. For example, the Exploratory Session template uses large text fields where you can define your Charter and Goals, and document notes, attach screenshots, and upload log files as you carry out your exploratory sessions.
Out of the box, TestRail comes with three default test case templates:Įach test case template comes with a slightly different set of fields to support the specific type of testing you are trying to accomplish. TestRail test cases are one of the most powerful features of TestRail because they are completely customizable and support custom fields with a wide variety of data types.
0 kommentar(er)
