Skip to content

Home

Jump to bottom
viltbalint edited this page Oct 11, 2018 · 4 revisions

InstaCoverage continous integration (CI) demonstrator

This project demonstrates how to work with CI tools (in this example with Jenkis) and LabVIEW with the InstaCoverage unit testing tool. As an example we implemented a calculator application which provides the four basic arithmetic operations and tested with InstaCoverage focused on code coverage.

Step 1 - Set up the Jenkins environment

The main tasks of this step are as follows:

  • Add code repository to Jenkins environment.

    • This demonstrator's code is available on our public GitHub repository.

  • Configure trigger action in Jenkins server.

    • In this demonstrator the trigger action is a new commit in the repository.

  • Configure todos upon each trigger (new commit) in a Jenkins file. In this demonstrator we configured following todos:

    • Checkout repository (default, not in file).
    • Run LabVIEW script to execute unit tests (see Step 2).
    • Display test execution results.

For further questions contact us at [email protected].

Step 2 - Set up LabVIEW script for executing InstaCoverage

The script is written in LabVIEW and it is used to execute the unit test environment for Jenkins. Our demonstrator contains an example script file, which executes the following actions:

  • Execute InstaCoverage's "Run Tests From Project" API VI to execute all InstaCoverage tests from our calculator project.
  • Execute InstaCoverage's "Generate Report File" API VI to create a JUnit test execution report.
  • To be able to display test coverage results we adapt the XML report for the built-in JUnit Jenkins plugin (the corresponding code be found here). Note that InstaCoverage's report format contains test coverage data.
  • Close LabVIEW.

Notes:

  • For the script VI to be executed automatically set the VI properties/Execution/"Run when opened" checkbox to true.
  • For displaying test coverage data another option would be create a new Jenkins plugin which is compatible with XML output format of InstaCoverage.

Step 3 - Actual usage: Commits and tests in the Calculator example project

As mentioned in the introduction section we developed a simple calculator application which demonstrates a possible software development process. As a first step we added the business logic of the calculator (3.1 and 3.2), then we started to add unit tests (3.2). At this point we realized that we didn't cover all VI diagrams (3.3). Because of our development process requires 100% diagram coverage for all VIs, we added the missing unit tests. As result of this it turned out that we have a bug in the implementation, which has to be fixed (3.4).

3.1 Initial implementation

Add basic functionality without unit tests.

Related build available here.

3.2 Initial implementation of tests

Functionality implementation and unit testsing.

Related build available here.

3.3 Test uncovered diagrams

Add new unit test to reach 100% diagram coverage and realize that our code is buggy.

Related build available here.

3.4 Fix implementation error

Fix functionality which doesn't meet the requirements.

Related build available here.

Clone this wiki locally