-
[This ticket was copied from the old sourceforge tracker, original issue created Feb 21 2008]
Currently, the only way to stop tests that are being run using JUnitCore,
is to implement a Runner that th…
-
```
Because your system has a hard requirement to use the new test runner, it will
be unusable in our Continuous Integration environment without having to go back
and write a custom parser or mergin…
-
```
Because your system has a hard requirement to use the new test runner, it will
be unusable in our Continuous Integration environment without having to go back
and write a custom parser or mergin…
-
```
Because your system has a hard requirement to use the new test runner, it will
be unusable in our Continuous Integration environment without having to go back
and write a custom parser or mergin…
-
```
Because your system has a hard requirement to use the new test runner, it will
be unusable in our Continuous Integration environment without having to go back
and write a custom parser or mergin…
-
```
Because your system has a hard requirement to use the new test runner, it will
be unusable in our Continuous Integration environment without having to go back
and write a custom parser or mergin…
-
```
Because your system has a hard requirement to use the new test runner, it will
be unusable in our Continuous Integration environment without having to go back
and write a custom parser or mergin…
-
```
Because your system has a hard requirement to use the new test runner, it will
be unusable in our Continuous Integration environment without having to go back
and write a custom parser or mergin…
-
```
Because your system has a hard requirement to use the new test runner, it will
be unusable in our Continuous Integration environment without having to go back
and write a custom parser or mergin…
-
```
Because your system has a hard requirement to use the new test runner, it will
be unusable in our Continuous Integration environment without having to go back
and write a custom parser or mergin…