runtimeverification / runtimeverification/kontrol
Better error origin tracing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
I was recently working with a test that had a number of assert(...)s that should be established at the end, and I had a failing branch in which I could not easlly understand which assert was failing. @anvacaru, would the recently introduced tracing mechanism record this info? @RaoulSchaffranek, how would Symbolik do in these situations?
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 by reviewing the recently introduced tracing mechanism and reproduce the described test with several assert(...) calls and a failing branch. Investigate whether it records which assertion failed, and compare the expected behavior with the Symbolik question raised in the issue. Done means a defined approach for identifying the failing assertion origin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100