runtimeverification / runtimeverification/kontrol
Improve Kontrol tests interface for profiling
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
As mentioned by @geo2a and @tothtamas28 today, we should make it easier for the backend team to do performance profiling using Kontrol integration tests. For that, we should
- identify tests that are most representative (e.g., I believe that the end-to-end tests repeat some integration tests)
- have an easier-to-use single pytest invocation for such tests
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 Kontrol integration tests and end-to-end tests, then compare them to identify representative cases and duplicated coverage. Design a single pytest invocation for the selected tests; done means the backend team can run those profiling-focused tests through one easy command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100