Testing Overview

EdgeX testing is focused on ensuring that the functional aspects of EdgeX work correctly. This level of testing includes a number of automated test suites for unit, integration, black-box, API testing and validation. Also, Edgex has been tested on TAF, which stands for Test Automation Framework. To monitor the stability and efficiency of Edgex, a Jenkins pipeline has been built to automatically trigger daily and weekly jobs. The testing processes are listed below. 

PR merge validation

When developers make changes to Edgex and open a PR, they have to go through unit test to check if it's fit to use before merging into main branch.

 After merging into the main branch, go modules and Service will build images on dockhub and snap. 

• Go modules
  • Unit test
• Service
  • Unit test 
  • Image build validation: snap image/ docker image
• edgex-compose
  • smoke test by TAF

Functional-test

• Purpose: Test each feature of Edgex by providing the appropriate input and validating the output against the requirements
• Frequency: Daily scheduled run on edgex-taf-pipeline

Integration-test

• Purpose: Check data communication among different software modules
• Frequency: Daily scheduled run on edgex-taf-pipelines

Performance-test 

• Purpose: Monitor memory usage/ startup time/ CPU usage/ response time/ event exported time of Edgex
• Frequency: Weekly scheduled run on edgex-taf-pipelines
• Note: When a new version of edgex is released, we will run performance tests on real hardware to test its efficiency and update the reports for each release here.

Smoke-test

• Purpose: Validate the most vital functions of EdgeX
• Frequency: Only when edgex-compose PR is opened will smoke-test start running.

Reference

• Edgex-go: https://github.com/edgexfoundry/edgex-go
• Edgex-taf: https://github.com/edgexfoundry/edgex-taf
• Edgex-compose: https://github.com/edgexfoundry/edgex-compose
• Edgex-taf-piplines: https://github.com/edgexfoundry/edgex-taf-pipelines