Note that the unit tests will provide quite a good test of quite of lot of this. A. Test upgrade Before you start, create a quiz using CBM, and make at least one attempt as a student. Upgrade should add a maxfraction column to question_attempts table. B. Deferred feedback with CBM - single question Preview a multiple-choice question using Deferred feedback with CBM behaviour. Set max mark to 1. Initially it should say Base mark 1 in the grey info area. If you loook in the technical info, it should say minfaction -6 and max fraction 3. There should be a help icon by the certainty choices. Check it out. Answer the question, getting it right and wrong with various levels of certainty (including forgetting to set one.) Check the 'CBM mark' in the grey info area against what the help says should happen. C. Immediate feedback with CBM - single question Repeat B, but for the 'Immediate feedback with CBM' behaviour. D. Use in a quiz Now create a quiz using either of the CBM behaviours. (It is enough to test just one.) Ensure that all the review options are turned on. Add several multiple choice questions (ideally about 10), and set some of them to have a Max mark different from 1. Attempt the quiz as a student, and get various questions right or wrong with different levels of certainty, and submit. On the review page, at the top, there should be some interesting statistics about how you did. Ensure they look OK. Make several more attempts. In terms of the judgement, you should be able to get it to say 'No questions', 'under-confident', 'a bit under-confident', 'OK', 'a bit over-confident' and 'over-confident'. As teacher, change the reivew options to remove 'Marks', but leave everything else on. Go back to the review page for an attempt as a student. The detailed score statistics should now not be shown. E. Re-grading old attempts. Go to the quiz you attempted in A. Look at the Results -> Grades report. The grades should not have changed. Re-grade the attempt. The grades will now change to the new values. Review the attempt, and check that is OK. F. Developer info Read question/engine/upgrade.txt and question/behaviour/upgrade.txt and check they make sense. G. Verify no regressions We might just rely on the 2.6 QA testing cycle for this, but do a spot check of some other parts of the quiz UI, and some other question behaviours, to make sure nothing is badly broken. H. ... and finally If you get this far, you deserve a beer.