Changes for page Testing
Last modified by Vincent Massol on 2023/10/26 15:34
From version 145.1
edited by Vincent Massol
on 2019/02/04 15:16
on 2019/02/04 15:16
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -13,7 +13,7 @@ 13 13 * Code committed must have associated automated tests. 14 14 * There are [[checks in the build>>Community.Building||anchor="HAutomaticChecks"]] (in the ##quality## profile - executed automatically on the CI) to ensure that committed code: 15 15 ** do not reduce the total test coverage for that module 16 -** do not decrease te mutation score for that module. Note: We use mutation score as a metric to gauge the quality of our tests. 16 +** do not decrease the mutation score for that module. Note: We use mutation score as a metric to gauge the quality of our tests. 17 17 * Developers run unit and functional tests on their machines daily and frequently. 18 18 * Unit and functional tests are executed by the CI, at each commit. 19 19 * Most automated functional tests are currently running in a single environment (HSQLDB/Jetty/Firefox). However, we've started to use Docked-based testing to test automatically using several configurations and are migrating more and more tests to that. There are jobs in XWiki's CI that execute tests in all configurations regularly (not at each commit though but as much as possible).