When Something Still Goes Wrong

When Something Still Goes Wrong

Das Fido-Curriculum Klasse 1
Fido MetaCurriculum Structure

Defects have reached testers. A Feedback button on nearly every screen records where a report was made; each report gets an answer and is closed only with a note of what was done. A fix comes with the general rule it broke: a property of the mastery engine, or a numbered requirement whose history names the report.

Checks miss things, and defects have reached our testers, children among them. So the software is built to hear about it. Nearly every screen of the app and the explorer has a Feedback button. A report records by itself where it was made, so a tester only has to say what is wrong. Guides see what the children of their own class reported.

Each report gets an answer. For a mistake in the curriculum, a proposed correction can appear on the tester's own screen, and the tester says whether it fixes the problem; only a person's approval makes it permanent. For a fix in the code, the tester is told once it has shipped and asked whether things are better. No report is closed without a note that says what was done.

A fix alone is not enough. When a defect has reached a person, the fix must come with the rule it broke, written down so that it also holds for cases nobody has thought of. In the mastery engine, that rule is a property checked on every invented learner, wherever it can be stated as one. Elsewhere it is a numbered requirement in a spec, with a test that names it, and the spec's history records which report led to it. The rule is stated for every case of its kind, not only for the one that was reported.

Keine Aufgaben fĂĽr dieses Thema.