Introduce a new JUnit test category that lets us mark certain tests as not ready for execution. The test task in the individual project can then be configured to not run tests marked as `NotReady`. For the CI server builds, add a fullTest test task that simply runs tests as normal, and link it into the check task so it runs on builds. This is not perfect, as the class under test must still compile, so it must have at least the correct signatures of all the methods tested. Also, it may be worth finding a way to distribute the NotReady interface that doesn't require checking it into every project.
|
|
||
| 19 |
|
19 |
|
| 20 |
|
20 |
|
| 21 |
|
21 |
|
|
22 |
|
|
|
23 |
|
|
|
24 |
|
|
|
25 |
|
|
|
26 |
|
|
|
27 |
|
|
|
28 |
|
|
| 22 |
|
29 |
|
|
|
||
| 11 |
|
11 |
|
| 12 |
|
12 |
|
| 13 |
|
13 |
|
|
14 |
|
|
|
15 |
|
|
|
16 |
|
|
|
17 |
|
|
|
18 |
|
|
|
||
|
1 |
|
|
|
2 |
|
|
|
3 |
|
|
|
4 |
|
|
|
5 |
|
|
|
6 |
|
|
|
7 |
|
|
|
8 |
|
|
|
||
| 1 |
|
1 |
|
| 2 |
|
2 |
|
|
3 |
|
|
|
4 |
|
|
| 3 |
|
5 |
|
| 4 |
|
6 |
|
| 5 |
|
7 |
|
|
|
||
| 16 |
|
18 |
|
| 17 |
|
19 |
|
| 18 |
|
20 |
|
|
21 |
|
|
| 19 |
|
22 |
|
| 20 |
|
23 |
|
| 21 |
|
24 |
|
| 22 |
|
25 |
|
| 23 |
|
26 |
|
| 24 |
|
27 |
|
|
28 |
|
|
| 25 |
|
29 |
|
| 26 |
|
30 |
|
| 27 |
|
31 |
|
|
|
||
| 32 |
|
36 |
|
| 33 |
|
37 |
|
| 34 |
|
38 |
|
|
39 |
|
|
| 35 |
|
40 |
|
| 36 |
|
41 |
|
| 37 |
|
42 |
|
|
|
||
| 42 |
|
47 |
|
| 43 |
|
48 |
|
| 44 |
|
49 |
|
|
50 |
|
|
| 45 |
|
51 |
|
| 46 |
|
52 |
|
| 47 |
|
53 |
|
|
|
||
| 50 |
|
56 |
|
| 51 |
|
57 |
|
| 52 |
|
58 |
|
|
59 |
|
|
| 53 |
|
60 |
|
| 54 |
|
61 |
|
| 55 |
|
62 |
|
| 56 |
|
63 |
|
| 57 |
|
64 |
|
|
65 |
|
|
| 58 |
|
66 |
|
| 59 |
|
67 |
|
| 60 |
|
68 |
|