Continuous Integration testing provides a critical tool to ensure that regressions (breakages with the introduction of new changes) do not occur in the code base. In this work package with will migrate the integration testing suite to use the GitHub Actions system for automating tests. The goal will be to automatically prevent the merging of any changes if the test framework does not pass. In addition, we will use any remaining hours in this deliverable to make other improvements to the testing framework such as expanding the number of tests, automatic creation of build artifacts (that can be downloaded and tested in a user’s local QGIS session) and ensuring that the test framework uses latest current best practice for the QGIS project.
Steps:
Samweli to perform a quick review of which framework to use
Any new functionality entering into the codebase should be accompanied by test
Retroactively add tests for key components like land cover class functionality
GUI testing is also needed so we need to review options e.g. Victor Olaya’s test tool versus Qtest framework, versus other test frameworks.
Samweli
commented
2 years ago
Continuous Integration testing provides a critical tool to ensure that regressions (breakages with the introduction of new changes) do not occur in the code base. In this work package with will migrate the integration testing suite to use the GitHub Actions system for automating tests. The goal will be to automatically prevent the merging of any changes if the test framework does not pass. In addition, we will use any remaining hours in this deliverable to make other improvements to the testing framework such as expanding the number of tests, automatic creation of build artifacts (that can be downloaded and tested in a user’s local QGIS session) and ensuring that the test framework uses latest current best practice for the QGIS project. Steps: