-
@baev, I've created a simple implementation of RunListener using `4.13-SNAPSHOT` and noticed my implementations for `testSuiteStarted` and `testSuiteFinished` are actually called twice. Looking at the…
-
Currently JUnit test categories can only be classes. In the maven configs you put the class name, and on the JUnit tests you put the actual class.
This forces you to put the Category class on a jar …
-
The status of the commit gets updated when the build is trigged and started. I see this in the jenkins logs:
```
GitHub pull request #3492 of commit b56319e17ce84c9cca7f312f18327007be91a410, no merge…
-
```
What steps will reproduce the problem?
Run the script shown at the bottom
i.e.
1. Add a RunListener to an instance of JUnitCore
2. Run a parameterised test with N parameters
3. Let all tests fail…
-
```
What steps will reproduce the problem?
Run the script shown at the bottom
i.e.
1. Add a RunListener to an instance of JUnitCore
2. Run a parameterised test with N parameters
3. Let all tests fail…
-
Using 1.638 and Mattermost 2.1, I'm only seeing notifications for when builds start. No other notifications appear to be sent.
-
Otherwise it is sometimes difficult to analyze the test timeout reported by our CI server - e.g. #3138
We could write a JUnit `RunListener` that prints the full thread dump when the test fails with …
-
The following build failed due to a test failure: (http://build-us-00.elastic.co/job/es_core_master_medium/3130/)
```
[12:04:04][~/code/esxp/elasticsearch]$ gradle :core:integTest -Dtests.seed=45D0AE…
-
```
What steps will reproduce the problem?
Run the script shown at the bottom
i.e.
1. Add a RunListener to an instance of JUnitCore
2. Run a parameterised test with N parameters
3. Let all tests fail…
-
See below the test class, with a dummy test doing nothing.
```
package my.package;
import org.junit.After;
import org.junit.Assume;
import org.junit.Before;
public class Test {
@Before
pub…