Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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, Service will build images on dockerhub and snap to validate its usage.

  • Go modules(Github)
    • Unit test
  • Service(Github????)
  • edgex-compose(move to smoke-test section ????)
    • 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

How to run functional-test on local?

https://github.com/edgexfoundry/edgex-taf/blob/main/docs/run-tests-on-local.md

Integration-test

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

How to run integration-test on local?

https://github.com/edgexfoundry/edgex-taf/blob/main/docs/run-tests-on-local.md

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 and update the reports for each release in here.

How to run performance-test on local?

https://github.com/edgexfoundry/edgex-taf/blob/main/docs/run-performance-metrics-collection-on-local.md

Smoke-test

  • Purpose: Smoke tests are tests selected by developers. They will select the tests that validate the most important features of EdgeX and run the smoke tests to check if it's good to go.
  • Frequency: Only when edgex-compose PR is opened will smoke-test start running.

Where is somke-test?

Example: https://github.com/edgexfoundry/edgex-taf/blob/f7c5ac7bf88c2cca21e5cb485ee655b14a2023d7/TAF/testScenarios/functionalTest/V2-API/core-metadata/deviceprofile/GET-Positive.robot#L15

In this example, only does ProfileGET001 - Query all device profiles have SmokeTest tag so smoke-test will run on this testcase only. 

Reference


  • No labels