test(first-traverse): prove FirstTraverseUnderTable blocks the post on its own

Open Beginner friendly
#3,094 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
69/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
testing

Research direction

Start with crates/app/tests/first_traverse_table.rs and the rig named a_head_tilt_past_90_under_the_table_is_refused_with_lower; check how it stays within the Z stroke while testing the FirstTraverseUnderTable verdict. Then read item 3 of docs/decisions/3081-table-down-axis-verdict.md for the expected plane verdicts. Done when a test proves this verdict alone blocks the post and the plane wording or displayed verdicts match the decision.

Written by the indexing model from the issue text.

Description

area:multiaxis effort:medium P7 source:agent

Follow-ups from the review of PR #3093 (#3081), comment 7053548122.

  1. In the refused-case rig of a_head_tilt_past_90_under_the_table_is_refused_with_lower (crates/app/tests/first_traverse_table.rs), the Z-stroke law also refuses the post. So no test shows that the new verdict FirstTraverseUnderTable alone blocks the post. Add a rig that stays inside the Z stroke and assert that the post error names this verdict.
  2. When the plane is above the stock top and no plane is clear, the operation shows only "lower the clearance plane". The "raise" verdict appears only after that repair. Both states refuse the post. Item 3 of docs/decisions/3081-table-down-axis-verdict.md says that both verdicts show: correct the wording, or show both verdicts at once.
Dominant language
Rust
Stars
8
Forks
11
Avg merge
8h 12m
Merged PRs (30d)
928

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 NeoTech/Camcraft

All issues in NeoTech/Camcraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.