Weblate testsuite and continuous integration Testsuites exist for most of the current code, increase coverage by adding testcases for any new functionality, and verify that it works. 450 Chapter 3. Contributor Release 4.18 3.9.1 Continuous integration Current test results can be found on GitHub Actions and coverage is reported on Codecov. There are several jobs to verify different aspects: • Unit tests • Documentation results of these scans at GitHub — they are stored as artifacts on our CI in the SARIF format (Static Analysis Results Interchange Format). See also: Continuous integration 3.13 Contributing to Weblate modules

Weblate testsuite and continuous integration Testsuites exist for most of the current code, increase coverage by adding testcases for any new functionality, and verify that it works. Continuous integration test results can be found on GitHub Actions [https://github.com/WeblateOrg/weblate/actions] and coverage is reported on Codecov [https://app.codecov.io/gh/WeblateOrg/weblate/]. There are several jobs results of these scans at GitHub — they are stored as artifacts on our CI in the SARIF format (Static Analysis Results Interchange Format). See also Continuous integration Contributing to Weblate modules

Weblate testsuite and continuous integration Testsuites exist for most of the current code, increase coverage by adding testcases for any new functionality, and verify that it works. 3.8. Reporting issues Release 4.16.3 3.9.1 Continuous integration Current test results can be found on GitHub Actions and coverage is reported on Codecov. There are several jobs to verify different aspects: • Unit tests • Documentation results of these scans at GitHub — they are stored as artifacts on our CI in the SARIF format (Static Analysis Results Interchange Format). See also: Continuous integration 438 Chapter 3. Contributor docs

Weblate testsuite and continuous integration Testsuites exist for most of the current code, increase coverage by adding testcases for any new functionality, and verify that it works. Continuous integration test results can be found on GitHub Actions [https://github.com/WeblateOrg/weblate/actions] and coverage is reported on Codecov [https://app.codecov.io/gh/WeblateOrg/weblate/]. There are several jobs results of these scans at GitHub — they are stored as artifacts on our CI in the SARIF format (Static Analysis Results Interchange Format). See also Continuous integration Contributing to Weblate modules

Weblate testsuite and continuous integration Testsuites exist for most of the current code, increase coverage by adding testcases for any new functionality, and verify that it works. 450 Chapter 3. Contributor Release 4.18.2 3.9.1 Continuous integration Current test results can be found on GitHub Actions and coverage is reported on Codecov. There are several jobs to verify different aspects: • Unit tests • Documentation results of these scans at GitHub — they are stored as artifacts on our CI in the SARIF format (Static Analysis Results Interchange Format). See also: Continuous integration 3.13 Contributing to Weblate modules

Weblate testsuite and continuous integration Testsuites exist for most of the current code, increase coverage by adding testcases for any new functionality, and verify that it works. 3.8. Reporting issues Release 4.17 3.9.1 Continuous integration Current test results can be found on GitHub Actions and coverage is reported on Codecov. There are several jobs to verify different aspects: • Unit tests • Documentation results of these scans at GitHub — they are stored as artifacts on our CI in the SARIF format (Static Analysis Results Interchange Format). See also: Continuous integration 442 Chapter 3. Contributor docs

Weblate testsuite and continuous integration Testsuites exist for most of the current code, increase coverage by adding testcases for any new functionality, and verify that it works. Continuous integration test results can be found on GitHub Actions [https://github.com/WeblateOrg/weblate/actions] and coverage is reported on Codecov [https://codecov.io/github/WeblateOrg/weblate]. There are several jobs results of these scans at GitHub — they are stored as artifacts on our CI in the SARIF format (Static Analysis Results Interchange Format). See also Continuous integration Contributing to Weblate modules

code, increase coverage by adding testcases for any new functionality, and verify that it works. 3.9.1 Continuous integration Current test results can be found on GitHub Actions and coverage is reported results of these scans at GitHub — they are stored as artifacts on our CI in the SARIF format (Static Analysis Results Interchange Format). See also: Continuous integration 3.12. Security and privacy 439 on November 5th 2022. • Added support for removing entries from translation memory. • Improved analysis on the duplicate language alert. • Improved accurancy of the consecutive duplicated words check

Weblate testsuite and continuous integration Testsuites exist for most of the current code, increase coverage by adding testcases for any new functionality, and verify that it works. Continuous integration test results can be found on GitHub Actions [https://github.com/WeblateOrg/weblate/actions] and coverage is reported on Codecov [https://codecov.io/github/WeblateOrg/weblate]. There are several jobs results of these scans at GitHub — they are stored as artifacts on our CI in the SARIF format (Static Analysis Results Interchange Format). See also Continuous integration Contributing to Weblate modules

Weblate testsuite and continuous integration Testsuites exist for most of the current code, increase coverage by adding testcases for any new functionality, and verify that it works. Continuous integration test results can be found on GitHub Actions [https://github.com/WeblateOrg/weblate/actions] and coverage is reported on Codecov [https://codecov.io/github/WeblateOrg/weblate]. There are several jobs results of these scans at GitHub — they are stored as artifacts on our CI in the SARIF format (Static Analysis Results Interchange Format). See also Continuous integration Contributing to Weblate modules