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 trigger jobs automatically. The testing processes are listed below.
When developers make changes and open PRs on EdgeX, they have to go through a different validation process depending on the type of repository.
https://github.com/edgexfoundry Type "go-mod" in the search field. All repositories whose titles contain "go-mod" are go-modules. |
https://github.com/edgexfoundry/edgex-go This repository contains the Go implementation of EdgeX Foundry microservices, such as core-data, core-metadata, support-notifications, etc. |
https://github.com/edgexfoundry/edgex-compose Smoke-test will be introduced later. |
https://github.com/edgexfoundry/edgex-taf/blob/main/docs/run-tests-on-local.md |
https://github.com/edgexfoundry/edgex-taf/blob/main/docs/run-tests-on-local.md |
Smoke-test
First, where is smoke-test? Example: https://github.com/edgexfoundry/edgex-taf/blob/f7c5ac7bf88c2cca21e5cb485ee655b14a2023d7/TAF/testScenarios/functionalTest/V2-API/core-metadata/deviceprofile/GET-Positive.robot#L15 Second, how to run smoke-test on local? Example: https://github.com/edgexfoundry/edgex-taf-pipelines/blob/5cb7fa71727f8b6c6470626ed0394a449b223b2c/runSmokeTestScripts.groovy#L32-L51 |