-
Notifications
You must be signed in to change notification settings - Fork 188
/
pom.xml
90 lines (79 loc) · 4.04 KB
/
pom.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
<?xml version="1.0" encoding="UTF-8"?>
<!--
~ Copyright (c) 2010-2017 Evolveum and contributors
~
~ This work is dual-licensed under the Apache License 2.0
~ and European Union Public License. See LICENSE file for details.
-->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<artifactId>midpoint</artifactId>
<groupId>com.evolveum.midpoint</groupId>
<version>4.1-SNAPSHOT</version>
</parent>
<groupId>com.evolveum.midpoint.testing</groupId>
<artifactId>testing</artifactId>
<packaging>pom</packaging>
<name>midPoint Testing Infrastructure</name>
<modules>
<module>sanity</module>
<!--
The following modules skip tests by default, but we ALWAYS want to build the sources.
That's why we don't want to add modules optionally based on profile.
Tests for selected modules are run in "long" CI build, see "extratest" profile lower.
Tests for a single module can be enabled by a property - skipXyTests=false semantic is used.
(I'd like to use "runXyTests", but that would require more POM code, sorry.)
See each POM for property controlling the tests - typically for "module-name" it's:
-Dskip<ModuleName>Tests=false (default value is true)
We try to avoid repeating "tests" in the property name, check its exact spelling in POMs.
If "skipXyTests" is set to false, property "skipTests" from command line is ignored
Property "skipITs" still works, but it doesn't make sense to use it as it goes against
the instruction to run the extra tests.
All extra tests are run by failsafe, so they are considered integration tests.
-->
<module>conntest</module>
<module>longtest</module>
<module>story</module>
<module>rest</module>
<module>samples-test</module>
<module>schrodingertest</module>
</modules>
<properties>
<!-- see notes in main midPoint POM -->
<!-- This applies to all testing submodules, all of them have only src/test, not main. -->
<maven.install.skip>true</maven.install.skip>
<maven.deploy.skip>true</maven.deploy.skip>
<!-- Properties controlling "extra" test modules. See "extratest" profile lower. -->
<skipConnTests>true</skipConnTests>
<skipLongTests>true</skipLongTests>
<skipRestTests>true</skipRestTests>
<skipSamplesTests>true</skipSamplesTests>
<skipStoryTests>true</skipStoryTests>
<!-- By default we skip Schrodinger tests. This is not part of "extra" tests. -->
<skipSchrodingerTests>true</skipSchrodingerTests>
</properties>
<profiles>
<profile>
<id>extratest</id>
<properties>
<!--
NOTE: To disable normal tests from default build (mvn clean install), we use
"skipTest" element - this repeats our intent from parent POM.
IT IS IMPORTANT to use this element to flip it back to "false" in POMs below.
If we use element "skip" and set it to false, skipTests is still "true" and the
whole testing is skipped. It's not necessary to define "skip" element, but it's
super-important to use "skipTests" consistently. Don't get burned like me.
-->
<skipTests>true</skipTests>
<!-- Conntests are not ready to run in "long" build yet. -->
<!--<skipConnTests>false</skipConnTests>-->
<skipLongTests>false</skipLongTests>
<skipRestTests>false</skipRestTests>
<skipSamplesTests>false</skipSamplesTests>
<skipStoryTests>false</skipStoryTests>
<!-- Schrodinger tests are separate, we don't want them in this profile -->
</properties>
</profile>
</profiles>
</project>