Figure out how to test QoS parameters
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 45
- Forks
- 57
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 2
Description
There are 2 branches currently in this repository that start adding QoS tests:
These should probably be combined, but then we run into a combinatorial problem; we would test all combinations of RMW implementations x the rclcpp or rclpy x all QoS parameters, which would lead to a very long test. What we should probably do is combine the above, and then choose some subset of the tests that make sense and run those.
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
Compare the qos-durability and qos_tests branches first, then review how their tests cover RMW implementations, rclcpp, rclpy, and QoS parameters. The work is done when the branches are reconciled and a practical, agreed test subset or matrix avoids the combinatorial test explosion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, 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