Changes for page Building XWiki from sources

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -216,12 +216,6 @@
216	216	** This is achieved using Jacoco and the check is done at each module level using a Maven property named ##xwiki.jacoco.instructionRatio##.
217	217	** Note: We also perform a global coverage check but [[it's done only in the CI>>dev:Community.ContinuousBuild#HCloverPipeline]]
218	218	* We check automatically that we don't have wiki pages that require Programming Rights unduly. This is exercised during functional tests. For more details see [[Testing documentation>>Community.Testing||anchor="HFunctionalTesting"]].
219		-* Verify that test quality doesn't go down (for ##xwiki-commons## and ##xwiki-rendering## ATM), using PIT/Descartes. Note that this takes time and thus is executed only in the ##quality## profile and only when the ##-Dxwiki.pitest.skip=false## system property/value is passed.
220		-** The check is done at each module level using a Maven property named ##xwiki.pitest.mutationThreshold##.
221		-** There are jobs on XWiki's CI that execute regularly to check this:
222		-*** [[xwiki-commons pitest job >>http://ci.xwiki.org/job/xwiki-commons_pitest/]]
223		-*** [[xwiki-rendering pitest job >>http://ci.xwiki.org/job/xwiki-rendering_pitest/]]
224		-*** [[xwiki-platform pitest job >>http://ci.xwiki.org/job/xwiki-platform_pitest/]]
225	225	* Verify Test output
226	226	** Verify that JUnit tests don't output content to stdout or stderr. Tests are supposed to either configure the code to not output anything or if it's expected then they're supposed to [[catch the logs and assert them>>dev:Community.Testing.JavaUnitTesting.WebHome#HCapturingandAssertingLogs]]. Note that this check is also executing for JUnit5 tests executed in your IDE (if the ##pom.xml## file in the current directory doesn't have the ##xwiki.surefire.captureconsole.skip## Maven property set to true).
227	227	** Verify that functional tests don't contain errors or warnings when they execute. See [[Docker Tests>>Community.Testing.DockerTesting.WebHome||anchor="HStdout2Fstderrvalidationerrors"]] (for JUnit5) and [[Selenium2 Tests>>Community.Testing.WebHome||anchor="HBestpractices"]] (for JUnit4).