Add testing-only operations that validate certain properties of the workflow

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
testing-qa

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.

Description

Before proceeding, is there an existing issue or discussion for this?
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 trim operations)
  • Count how many times an operation was reached per session
Dominant language
Rust
Stars
75
Forks
18
Avg merge
12d 12h
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-rmf/crossflow

All issues in open-rmf/crossflow

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.