Skip to content

Document testing and QA strategy for utilities #105

Description

@YurMil

Write a docs page defining how utilities are verified: unit tests for calculation engines, manual test checklists for file-based tools (DXF/STEP/PDF), and browser/WebGL support expectations (Chromium, WebGL 2, WASM).

Acceptance criteria:

  • Published under docs/guides
  • Referenced from CONTRIBUTING/README


This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #105 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @YurMil (replace 20 with the amount, and @YurMil with the user to tip).

📖 If you want to learn more, check out our documentation.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions