-
Notifications
You must be signed in to change notification settings - Fork 0
/
notes.txt
35 lines (29 loc) · 1.59 KB
/
notes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
Working models: Question, ArchiveQuestion
Using built-in user model (no need to add)
Need to work on Response, Test model
@login_required -> require a login for this function
QUESTIONS---
>>In ArchiveQuestion-- if user's response is tested by the Test class, where each question can have multiple tests
>> that (theoretically) all have different correct solutions, do we need the solution field in
>> the ArchiveQuestion class?
>>In views-- when updating attempt or creating a new response if none exists, is the response.save()
>> method needed? Same goes for updating the response in submit_response..
!!!!!!!!!!!!
Functions that don't take in any parameters (eg, a Hello World! function) cannot have tests, since adding tests requires that you enter arguments.
!!!!!!!!!!!!
user history -- figure out archiving, including tests with archives
first integrate unit tests with questions-- must validate unit tests with questions when question submitted
message to add unit tests if none there
form validations
deleting things (questions, test)
user submitted response, & question submission-- say which tests it failed
then user history
algorithm for question tracks:
mostly get questions @ current level
maybe give a few more difficult to see how it is
if they get a question right, maybe never see again, but see something similar
if they get it wrong, give again at some point
study mode which is tag based eventually too
text editor-- mdn orion
question submission: takes back to question edit page, w/message on top-- look @ message framework
catch AssertionError and give feedback message