Company Events Academic Community Support Solutions Products & Services Contact NI MyNI

Unit Test Framework Page (Project Properties Dialog Box)

LabVIEW 2013 Unit Test Framework Toolkit Help

Edition Date: June 2013

Part Number: 372584F-01

»View Product Info
Download Help (Windows Only)

Requires: Unit Test Framework Toolkit

In the Project Explorer window, select Project»Properties to display the Project Properties dialog box. Select Unit Test Framework from the Category list to display this page.

Use this dialog box to configure the testing options of a LabVIEW project.

This page includes the following components:

  • Filters—Specifies the types of filters to use when executing tests in a LabVIEW project, including executing tests by priority and modified tests.
    • Minimum priority—Specifies whether to execute only tests with a minimum test priority. If the Minimum priority checkbox contains a checkmark, LabVIEW executes only tests with an equal or higher priority than the Test priority you specified. By default, this checkbox does not contain a checkmark.
      • Test priority—Specifies the minimum priority of tests to execute. The highest priority is 1000, and the lowest priority is 0. The default is 5.
    • Modified tests and VIs—Specifies whether to execute only tests that have been modified since a specified time. By default, this checkbox does not contain a checkmark.
      • Last test execution—Specifies whether to execute only tests and VIs that have been modified since the last test execution.
        Note  You must configure the LabVIEW Unit Test Framework Toolkit to generate a test status log before you can use this filter.
      • Timestamp—Specifies whether to execute only tests and VIs that have been modified since a given date and time.
        • Date/time—Specifies the date and time after which LabVIEW checks to see if tests and VIs have been modified.
      • Last N days—Specifies whether to execute only tests and VIs that have been modified in the last N days, where N is the number you specify using the N control.
        • N—Specifies the number of days after which LabVIEW checks for tests and VIs that have been modified. The default is 1.
      • Include tests of all caller VIs—Specifies whether to execute tests of all VIs that call any of the modified VIs. By default, this checkbox does not contain a checkmark.
  • Generate Reports—Specifies the types of reports LabVIEW generates after test execution.
    • ATML/XML Report—Specifies the settings related to generating a report in Automatic Test Markup Language (ATML) format.
      • Generate ATML/XML report—Specifies whether LabVIEW generates a report in ATML format.
        • ATML/XML report file path—Specifies the path to the ATML file where LabVIEW generates this report.
          Note  By default, LabVIEW generates this report in the same directory as the project.
        • View report after execution—Specifies whether to display this report after test execution.
    • HTML Report—Specifies settings related to generating a report in HTML format.
      • Generate HTML report—Specifies whether LabVIEW generates a report in HTML format.
        • HTML report file path—Specifies the path to the HTML file where LabVIEW generates this report.
          Note  By default, LabVIEW generates this report in the same directory as the project.
        • Use user-defined CSS file—Specifies whether to use a user-defined Cascading Style Sheet (CSS) file to format HTML reports.
          • CSS file path—Specifies the path to the CSS file.
        • View report after execution—Specifies whether to display this report after test execution.
    • ASCII Report—Specifies the settings related to generating a report in ASCII format.
      • Generate ASCII report—Specifies whether LabVIEW generates a report in ASCII format.
        • ASCII report file path—Specifies the path to the ASCII file where LabVIEW generates this test report.
          Note  By default, LabVIEW generates this report in the same directory as the project.
        • View report after execution—Specifies whether to display this report after test execution.
  • Report Details—Specifies the contents of the test reports.
    Note   You must specify a report type in the Generate Reports section to use this section.
    • Report Contents—Specifies the contents of the test reports.
      • Summary data—Includes a summary of the number of tests that passed, failed, were skipped, or produced errors. By default, this checkbox contains a checkmark.
      • Failed tests—Includes information about tests that failed. By default, this checkbox contains a checkmark.
        • Include details—Includes detailed information about this type of test results, such as the path to the VI under test, test status, execution time, and test case results. By default, this checkbox does not contain a checkmark.
      • Passed tests—Includes information about tests that passed. By default, this checkbox contains a checkmark.
        • Include details—Includes detailed information about this type of test results, such as the path to the VI under test, test status, execution time, and test case results. By default, this checkbox does not contain a checkmark.
      • Skipped tests—Includes information about tests that LabVIEW skipped. By default, this checkbox contains a checkmark.
      • Errors—Includes information about errors that occurred during test execution. By default, this checkbox contains a checkmark.
        • Include details—Includes detailed information about this type of test results, such as the path to the VI under test, test status, execution time, and test case results. By default, this checkbox does not contain a checkmark.
    • Display By—Specifies whether to display the test results according to the names of the tests or names of the VIs. The default is to display by the test name.
      • VI name—Displays the results according to the names of the VIs.
      • Test name—Displays the results according to the names of the tests.
  • Generate Log Files—Specifies the types of log files LabVIEW generates during test execution.
    • Test Status—Specifies settings related to generating a test status log file.
      • Log test status—Specifies whether to generate a test status log file during test execution. This log file contains information about the most recent test execution and results. During execution, LabVIEW logs the test names, times of execution, durations of execution, and whether the tests passed (1), failed (0), produced errors (2), or were skipped (3). By default, this checkbox does not contain a checkmark.
        Note  LabVIEW uses the information in this log file to determine which tests to execute when you execute tests that have been modified since the last execution. You must generate this log file in order to execute only modified tests.
        • Test status log file path—Specifies the path to the file where LabVIEW saves this log file.
          Note  By default, LabVIEW generates this log file in the same directory as the project.
    • Test Execution—Specifies settings related to generating a test execution log file.
      • Log test execution—Specifies whether to generate a test execution log file during test execution. This log file contains information about the previous test execution(s). During execution, LabVIEW logs the entire execution process, including the test path, VI path, time of execution, running setup and teardown VIs, code coverage measurement, and test cases results. You can use this log file to troubleshoot tests that timed out, produced errors, or did not complete. By default, this checkbox does not contain a checkmark.
        Note  If you place a checkmark in this checkbox, LabVIEW appends the details of each subsequent execution to the existing log file unless you place a checkmark in the Overwrite log file checkbox or change the log file name.
        • Test execution log file path—Specifies the path to the file where LabVIEW saves this log file.
          Note  By default, LabVIEW generates this log file in the same directory as the project.
        • Overwrite log file—Specifies whether LabVIEW overwrites this log file during every execution. If you place a checkmark in this checkbox, LabVIEW replaces the existing log file with details from the current execution. By default, this checkbox does not contain a checkmark.
  • Test Creation—Specifies the settings related to creating .lvtest and .lvvect files.
    • Test File and Test Vector File Location—Specifies the settings related to the default location where LabVIEW saves new .lvtest and .lvvect files.
      • Change default location—Specifies whether to change the default location where LabVIEW saves new .lvtest and .lvvect files. By default, this checkbox does not contain a checkmark, and LabVIEW saves new .lvtest and .lvvect files in the same directory as the VIs under test.
        • Default location file path—Specifies the default directory where LabVIEW saves new .lvtest and .lvvect files.
          Note  If you specify a location in the same disk drive that contains the project under test, this control displays a relative path. Otherwise, this control displays an absolute path, which describes the location starting from the top level of the file system.
    • External Editor—Specifies the settings related to editing .lvtest and .lvvect files.
      • Change default editor—Specifies whether to change the default editor LabVIEW uses to edit .lvtest and .lvvect files. By default, this checkbox does not contain a checkmark, and LabVIEW uses Microsoft Excel as the default editor.
        • Default editor file path—Specifies the default editor LabVIEW uses to edit .lvtest and .lvvect files.
    • Configuration—Specifies the settings related to configuring VIs under test, setup and teardown VIs.
      • Input/output values—Specifies which controls and indicators of the VI under test appear on the Test Cases page of the Test Properties dialog box. You can select from the following options:
        • Include controls and indicators from connector pane (Default)—Displays the controls from the connector pane of the VI under test and setup VI as input and displays the indicators from the connector pane of the VI under test and teardown VI as output. You must select a connector pane pattern and assign terminals for the VI under test. National Instruments recommends this option when executing a test on a real-time (RT) target. Doing so avoids test errors that result if the RT target cannot find an input or output.
        • Include controls and indicators from front panel—Displays the controls from the front panel of the VI under test as input and displays the indicators from the front panel of the VI under test as output.
        • Include controls and indicators from front panel as both input and output—Displays the controls and indicators from the front panel of the VI under test as both input and output.
      • Capture input values—Specifies whether to capture the default input values from the VI under test when creating a test. By default, this checkbox contains a checkmark.
      • Capture output values—Specifies whether to capture the default output values from the VI under test when creating a test. By default, this checkbox contains a checkmark.
      • Maximum array elements—Specifies the maximum number of array elements that LabVIEW lists on the Test Cases page of the Test Properties dialog box. If an array contains more elements than the specified number, LabVIEW lists the array as one item. The default is 100.
        Note  If you change the Maximum array elements, you need to update each test case by clicking the Import Values from VI button on the Test Cases page.
      • Default array brackets—Specifies the characters LabVIEW uses to wrap control and indicator names of an array. The default is [].
      • Default name separator—Specifies the character LabVIEW uses to separate control and indicator names in a cluster. The default is /.
  • Test Execution—Specifies passwords to the project settings so you can execute tests on password-protected VIs. During execution, LabVIEW stores the passwords in the LabVIEW password cache and saves them in the project file (.lvproj). LabVIEW encrypts the passwords before saving them in the project file.

    You also can use this section to configure whether LabVIEW generates code coverage of the whole project and whether LabVIEW enables VI server on a real-time target.
    • Passwords—Specifies settings related to passwords.
      • Password(s) Currently Stored—Displays the number of passwords stored in the password list.
      • Password to Add—Specifies the password you want to add to the password list.
      • Add—Adds the password you specify in the Password to Add text box to the password list.
      • Clear All—Clears the password list from the project settings.
        Note  Clicking the Clear All button does not remove passwords from the LabVIEW password cache. You can remove passwords from the LabVIEW password cache by restarting LabVIEW or by clearing the password cache from the Environment page of the Options dialog box.
    • Execution—Configures the settings related to executing a test.
      • Digits of precision for floating-point comparison—Specifies the number of digits after the decimal separator that LabVIEW uses for comparing floating-point values. Valid values are 0-32. The default is 6.
      • Repetitions—Specifies the number of times that LabVIEW repeats the test. The default is 1.
      • Set timeout (s)—Specifies whether to set a timeout, in seconds, for the test during test execution. For example, you can set a timeout for tests of VIs that loop forever or require you to perform tasks manually. If the VI under test times out during execution, LabVIEW stops the VI and test results show this test as failed. By default, this checkbox does not contain a checkmark.
        • Timeout—Specifies the time limit, in seconds, in which LabVIEW must complete the test execution. If you place a checkmark in the Set timeout checkbox, the default is 0.
      • Set minimum code coverage (%)—Specifies whether to set a minimum code coverage requirement, in percent, for the VI under test during test execution. If the VI under test does not meet the minimum code coverage requirement during test execution, test results show this test as failed. By default, this checkbox does not contain a checkmark.
        • Code coverage—Specifies the percentage of subdiagrams LabVIEW must execute during test execution. If you place a checkmark in the Set minimum code coverage checkbox, the default is 100.
    • Include VIs that were not tested—Specifies whether LabVIEW opens all VIs in this project to count subdiagrams and generates the code coverage rate of this project.
      Note  If this project contains a large number of VIs, opening these VIs can slow performance.
    • Enable VI Server on real-time targets—Specifies whether to enable the VI Server when you run this test on an RT target. You must enable the VI server to execute unit tests on an RT target. LabVIEW disables the VI server on the RT target when the test completes. You also can manually enable or disable the VI server on an RT target by configuring the VI server for the RT target.

 

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
Add Comments 1 2 3 4 5 submit