CoveredTestResultPerTestMethod API#95
Conversation
Signed-off-by: André Silva <andre15andre@hotmail.com>
Signed-off-by: André Silva <andre15andre@hotmail.com>
Signed-off-by: André Silva <andre15andre@hotmail.com>
Signed-off-by: André Silva <andre15andre@hotmail.com>
Signed-off-by: André Silva <andre15andre@hotmail.com>
|
If you want to review the current state of the PR, the content shouldn't change much. I'm working on a few more test cases to cover everything new, cleaning and documenting the code. |
|
Cool, thanks @andre15silva. @danglotb would you be available for a code review? |
Because CoverageFromClass was not serializable, loading a serialized CoverageDetailed object was not possible. Signed-off-by: André Silva <andre15andre@hotmail.com>
Signed-off-by: André Silva <andre15andre@hotmail.com>
Signed-off-by: André Silva <andre15andre@hotmail.com>
Signed-off-by: André Silva <andre15andre@hotmail.com>
Signed-off-by: André Silva <andre15andre@hotmail.com>
|
PR ready for review. I have a pending issue with |
danglotb
left a comment
There was a problem hiding this comment.
Overall the changes look good to me.
However, I have to open question for the future of `test-runner :
- I'm asking myself if we could reduce the code redundancies by encapsulating a
TestResultImplin theCoveredTestResultPerTestMethodImplto avoid a bit the redundancies. - Should we keep
CoveragePerTestMethodandCoveragesince we have now a richer object for the same "price", i.e.Coverage+TestResult?
I'll merge the changes ASAP the CI is ok.
Thank you for your contributions! Good job
|
You increased the coverage! https://coveralls.io/jobs/82527638 Thank you |
This PR introduces a new API in
test-runner'sEntryPoint.It's purpose is to return a
CoveredTestResultPerTestMethodobject, which contains the information relative to the coverage per test method, as well as the test execution results.