9798-5Revision CheckerISO/IEC DIS 9798-5
01The record02Free check 03Revision04Dated plan 05Kit and watch06Rules by market 07Answers

Home / The record / Annexes

Annex D

Numerical examples as a regression test

ISO/IEC DIS 9798-5 · Annexes · extended

Annex D is informative and gives worked numerical examples. They are the cheapest regression test in the part, because they turn a formula into a value that either matches or does not. The fourth edition will reissue them for the revised text.

What it asks
Run the examples against the implementation and keep the output with the release record, and add any local parameter set to the same test. Where an example does not match, record the difference as a defect rather than adjusting the expected value.
What the revision does
The fourth edition will update the examples. The revised values are not public. The annex keeps its 2009 material and gains the revision, which a copy of the older annex will not have.
Who it binds
The test owner and the release manager.
Evidence an auditor samples
  • The example runner and its expected values (test suite)
  • The last run output, dated, with the edition it used (release record)
  • The defect record for any mismatch (issue tracker)
The test you can run
Run the examples on a clean build. A pass on one family and a skip on another is a finding, not a partial pass.
Common failures
  • The examples are run once by hand and never in the pipeline.
  • A mismatch is resolved by changing the expected value.
How to close it
Put the examples in the pipeline and make the release record quote the run. It is the highest value test per line of code in a mechanism change, and it catches the arithmetic drift that reviews miss. The artefact that opens the work is the example runner and its expected values; the row is only closed when that artefact is dated and has a person against it.
Where it sits against the 2009 edition
Annex status: the 2009 edition carries it, and the revision carries forward it. The citation therefore has to name the edition.

For the file, this row closes when the example runner and its expected values exists with a date, a named holder and a pointer, and when the test above has been run and recorded. The test owner and the release manager. owns that answer for Annex D.