Check that student answers continue to be saved while progressing through a test: create a 10 question test (one question per page), start taking it as a student, answer the first 5 questions then close browser without submitting. Open browser, login again as student, restart test, check that answers were saved.

Performance test:

Check that response time does not decrease linearly when progressing through a large test.

Enable mysql query logging on db and count the number of UPDATE queries while progressing through a test.

Load test:
It would be something along these lines using selenium or other scripting tool in order to simulate large numbers of students taking a test at the same time (300-400). Google Testing Sheet

Functional test:
Check that student answers continue to be saved while progressing through a test: create a 10 question test (one question per page), start taking it as a student, answer the first 5 questions then close browser without submitting. Open browser, login again as student, restart test, check that answers were saved.
Performance test:
Check that response time does not decrease linearly when progressing through a large test.
Enable mysql query logging on db and count the number of UPDATE queries while progressing through a test.
Load test:
It would be something along these lines using selenium or other scripting tool in order to simulate large numbers of students taking a test at the same time (300-400). Google Testing Sheet

Description

Stephen wrote to the list today:

I think the total number of questions in the assessment is the issue here. If you graph database activity, you’ll see that the number of update queries increases as students progress through an assessment, because T&Q updates the scoring each time an item is saved and I suspect it updates every item in the assessment.