| | 79 | |
| | 80 | === Integrate testing framework with !GitHub Actions === |
| | 81 | |
| | 82 | * The testing framework was written before migration to !Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, different goals overall were prioritized. |
| | 83 | * An update is needed to reflect that tests are used to evaluate pull requests (PRs). |
| | 84 | * Most of the updates should be generic enough to integrate well with any CI environment. However, currently GRASS GIS is using !GitHub Actions which open the possibility to make use of specific features there, e.g., upload artifacts for failed tests or do a quick test only of files changed in the PR. |
| | 85 | * Possibly, use //pytest// (following example of GDAL and Numpy) instead of Python unittest (some parts of grass.gunittest might be replaced by or ported to pytest). |
| | 86 | * Current tests don't accommodate well tests of the main GRASS executable (which is now more prominent also because `grass ... --exec`). |
| | 87 | * Both preserving and removing of existing HTML reporting functionality are valid options. |
| | 88 | |
| | 89 | * Requirements: Python, !GitHub Actions (YAML configuration) |
| | 90 | * Mentor: Vaclav Petras |
| | 91 | * Proposed by: Vaclav Petras |
| | 92 | * Rating: medium |
| | 93 | * Expected Outcomes: Effective reporting of test results in pull requests |
| | 94 | * Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too. |
