Importing requirement files

To link a test case or a service to the requirements, you must first import into your project the requirements that come from other tools.

Before you begin

HCL OneTest™ Embedded supports the following requirement file formats:
  • ReqIF format (see https://en.wikipedia.org/wiki/Requirements_Interchange_Format). The extension is .reqif.
  • ReqIFz format: A zip file is required and must contain at least one ReqIF file. The extension is .reqifz.
  • CSV format: In the CSV file, the first row must contain the column names and the next rows must contain the data. The CVS file must have the following columns:
    • Id: Identifier of the requirements. This column is mandatory.
    • Parent: Id of the parent requirement. This column is optional. If this column is not present, all requirements are set at the top level.
    • Name: Name of the requirement. This column is optional.
    • Description: Description of the requirement. This column is optional.
    • Add other columns as required.

Procedure

To import a requirement file into your project, follow these steps:
  1. Click Settings in the Project Window.
  2. In the left panel Configuration properties, select Requirements.
  3. In the right panel, click the Value field of the Requirement files setting (the default value is blank) and click the … button.
  4. In the file browser that opens, select one requirement file and click Open.
  5. Optional: To add more than one requirement file, import an additional requirement file into the project tree as follows:
    1. Right-click the root node and click Add Child > Files….
    2. In the file browser that opens, select a requirement file and click Open.

      The file is added to the tree and is considered as an additional requirement file when the requirement traceability matrix is generated.

  6. To select attributes for the requirements so that they are added to the traceability matrix report, proceed as follows:
    1. Click Settings in the Project Window.
    2. In the left panel Configuration properties, select Requirements.
    3. In the right panel, click the value of the Attributes settings (the default value is blank) and enter a list of ReqIF attributes separated by a coma. For each of them, enter a new name as follows so that they are all displayed in the report: <ReqIF attribute name>:<new name>.
  7. You can enter other requirement settings as follows:
    • In Report Template, you can change the template of the report. By default, the template is named reqreport.template and it is saved in the lib/reports folder.
    • In All attributes, select 'yes' if you want to generate all the attributes in the JSON file. The default value is 'no'.
    • In Non-terminal requirements covered by children, if you select 'yes', a non-terminal requirement can be covered if all its children are covered. If you select 'no', a non-terminal requirement must be covered at least by one test case.

What to do next

After you import the requirement files into your project, you can link test cases or services to the requirements in your project. See Linking tests to requirements.