-
Notifications
You must be signed in to change notification settings - Fork 9
Testing
Testing must be a two-track work:
- software testing of the server
- software and didactic testing for the exercises
Each function/method must have a doctest string testing the definition of the function against what it does.
Each module/file must hava a django-test associated with it to test the funcionality of the module against it's documentation.
Each feature must be associated with a use case or user story a successfully writen feature is one with a test showing that the feature is executed (successfully) in a given user story.
A feature: something a user can perceive when using the software. This is very general but what the user is seeing is the reality of the software.
The idea in those are functional testing of the exercise, "Is the code of the exercise correct", "did the changes in the platform changed the way the exercise is working".
Exercise-level-tests SF-level-tests
The question in the didactic testing of exercises is not a really a software test but some feedback should be done to the creator of an exercise.
The questions asked here must be answered in the statistical analysis of answers.