Add testing-only operations that validate certain properties of the workflow
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Before proceeding, is there an existing issue or discussion for this?
- I have done a search for similar issues and discussions.
Description
The extreme extensibility of how operations are designed means that we could provide some operations in the testing module that are purely for testing purposes, to validate that other operations are working as intended. This will be a running list of possible testing operations:
- Verify that an operation was cleaned as intended (useful for testing
trimoperations) - Count how many times an operation was reached per session
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 locating the Rust testing module and reviewing how operations are defined, reached per session, and cleaned. Determine the intended behavior for an operation that verifies cleanup and one that counts session reach events. Done means both testing-only operations can validate those properties for other operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100