runtimeverification / runtimeverification/kontrol
Align `kontrol` to `forge` behavior
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
We should make sure that whenever we have an intersection between kontrol and forge functionality, commands, and their options, kontrol should behave similarly to forge.
One example is being addressed in https://github.com/runtimeverification/kontrol/pull/103 is the test selection functionality in forge test/kontrol prove:
forge testanalyzes all tests matching a regex provided with--match-testoptionkontrol buildverifies a single test supplied with--test
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 reading PR 103 and comparing the forge test/kontrol prove test-selection behavior described here, including --match-test and --test. Then identify other overlapping forge and kontrol commands or options covered by the issue. Done means the relevant kontrol behavior matches forge across the agreed overlaps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100