qa-of-code-guidance icon indicating copy to clipboard operation
qa-of-code-guidance copied to clipboard

Published 20 hours ago • verified publisher icon best-practice-and-impact

Expand testing chapter

Open foster999 opened this issue 1 year ago • 4 comments

foster999 avatar Sep 09 '22 15:09 foster999

Relates to #29

foster999 avatar Sep 09 '22 15:09 foster999

Links to #116

RuSnook avatar Feb 17 '23 10:02 RuSnook

Links to #128

joshlynchONS avatar Mar 01 '23 16:03 joshlynchONS

Provisional headings:

  • Write tests as code
  • Structure test files to match code structure
  • Run tests against all code changes
  • Write reproducible tests
  • Use minimal and realistic test cases
  • Test that new logic is correct (unit tests)
  • Test that different parts of the code interact correctly (integration tests)
  • Test that the whole system works (end to end tests)
  • Test that user needs are met (user acceptance tests)
  • Minimise repetition in test code (fixtures and parameterised tests)
  • Write tests before writing logic (TDD)
  • Write tests to ensure that bugs are fixed

Should mention in intro that testing assumes that code is packaged

foster999 avatar Apr 20 '23 11:04 foster999