For some exercises using JaCoCo (like Coverage), it may be useful to specify advanced xpath(s) for the report in XML to better compute what should be covered (or not), instead of relying on the "total" count : it is now possible with the new key coverage_xpaths in feedback_settings.yaml page :
If not specified, the used value will be the previously one used in the code ( ["./counter"] )
Checklist :
✔️ add tests in check_requirements.py
✔️ add code that doesn't break backwards
❌ add documentation about that in feedback_settings.yaml page
🚧 need to be tested in real life : since Inginious seems to have some problems with the java8scala environment, whatever the version I used (v5 or v6), cannot test myself 👎
Hello LEPL1402,
For some exercises using JaCoCo (like Coverage), it may be useful to specify advanced xpath(s) for the report in XML to better compute what should be covered (or not), instead of relying on the "total" count : it is now possible with the new key
coverage_xpaths
in feedback_settings.yaml page :For example :
If not specified, the used value will be the previously one used in the code (
["./counter"]
)Checklist : ✔️ add tests in check_requirements.py ✔️ add code that doesn't break backwards ❌ add documentation about that in feedback_settings.yaml page 🚧 need to be tested in real life : since Inginious seems to have some problems with the java8scala environment, whatever the version I used (v5 or v6), cannot test myself 👎