Peer Feedback Response to #278: No clear pass or fail criteria for many tests

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active

Research direction

The issue names test IDs SFT-2.6, SFT-2.4, SNFT-1.1, SNFT-2.1 and SNFT-2.2, which are defined in the test documents rather than in code, and it refers back to peer feedback in #278. Start by reading #278 and locating those test entries to see how their pass/fail criteria are written. Done means each named test has objective criteria tied to what the system must do, and the non-functional tests have checks beyond tester opinion.

Written by the indexing model from the issue text.

Description

documentation Feedback Response Revision

Description of the Feedback

Pass or fail criteria isn't objective for certain tests or verify what the test is actually supposed to

Actions to be taken

  • review tests SFT-2.6, SFT-2.4
  • revise pass/fail criteria to be more exact and pass only if the test verifies does exactly what the system is supposed to
  • Review SNFT-1.1, 2.1 and 2.2 and find ways other than solely tester opinion for pass/fail criteria
Dominant language
TeX
Stars
0
Forks
0
Avg merge
1d 7h
Merged PRs (30d)
52

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 Aeolus-Software/RealmForge

All issues in Aeolus-Software/RealmForge

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.