-
Hope all is well! Spotted our first issue on this project literally ever!
If you have a test which throws an exception - and then an @After after the test runs, any exception from the test is only pr…
-
```
What steps will reproduce the problem?
1. Create a project like the attached screenshots and files
2. Run tests using JUnit (reproducable with IntelliJ IDEA and Maven)
What is the expected output…
-
```
What steps will reproduce the problem?
1. Create a project like the attached screenshots and files
2. Run tests using JUnit (reproducable with IntelliJ IDEA and Maven)
What is the expected output…
-
```
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…