runtimeverification / runtimeverification/kontrol
Include `kontrol prove` command in the XML report
Open
Nobody has claimed this yet.
engagement
enhancement
kaas
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
As suggested by @lisandrasilva, we might want to include the kontrol prove command that generated this report into the XML report (so we can see what flags were used). And also, if the test-suite belongs to a GH repo, what is the commit-hash corresponding to the generated report.
For instance:
<testsuites tests="24" failures="2" errors="0" time="3227.6390516757965" timestamp="2024-09-25 14:55:28.227190" kontrol-cli-cmd= "kontrol prove --maintenance-rate 24 --xml-test-report" commit-hash="26677b899f162392c8f4a30ef4e8800f4a030613">
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the kontrol prove command and the XML test-report generation path. Trace how the command options and repository context reach the report, then verify that the generated <testsuites> element includes the invoked command and the corresponding GitHub repository commit hash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100