Load test results into DB#43
Conversation
…m generated tests between pairs of providers
|
There are some discrepancies between the test classes in the |
|
Indeed there are 19 JUnit4 reports that failed parsing: Looking at the example of Next steps:
|
|
There are now no tests that JaCoCo picks up but not our test result parsing: Though there are still the same 40 tests missing in the other direction: |
|
Looking at the first one, The test succeeds, unsurprisingly: But no |
|
In fact, 38 of the 40 are in the same situation. I gathered all relevant generated test source names with Interestingly it has generated a Its test output is a failure, but it looks "normal": The underlying issue is that |
|
As it's a single test that triggers this We can now easily find all 60 individual test methods that fail for one provider but not another: |
…another, another for finding methods that were covered by one provider's tests but not another's
…esults into the DB
The JaCoCo coverage results are already in the DB; in order to figure out which coverage differences do not correspond to differences in test results, we need to get the latter into the DB too.