| Age | Commit message (Collapse) | Author |
|---|
|
- Add error message details to SeleniumTestError
- Fix next question cycling in models
- Fix model test cases
|
|
- Fix movement from one question to another in next_question
- Fix random display of errors from MCQs
- Add Notification display if question has been attempted
- Fix test cases for changes made
|
|
|
|
|
|
1. Due to the new evaluator, an unchecked bug, which marked all mcq and mcc attempts as correct, despite actually marking the wrong answer, has been fixed.
2. Added Test case to check for incorrect mcq and mcc questions
3. question.html would also render error msg for mcq and mcc questions. This has also been fixed.
|
|
|
|
|
|
|
|
- Modify grade user html template to create readable variables for answer and error
|
|
- Question should skip to new question with new error rendering
- Fix test cases
Fix change_dir context manager in grader
|
|
- Error are sent as list
- Error are None if answer is fully correct
- Error is rendered as in grade user and code questions as neat CSS divs
- Fix corresponding test cases
- Fix get_question answers in models.py
|
|
- code_evaluator module and class renamed to grader
- Test cases fixed
- Comments removed
- weight variable renamed to mark
|
|
|
|
Question form interface
|
|
|
|
|
|
|
|
partial grading
|
|
|
|
|
|
|
|
|
|
While testing regrade method for code questions, code server needs to
serve.
|
|
regrade_papers
Resolved
Conflicts:
yaksh/models.py
yaksh/test_models.py
yaksh/urls.py
yaksh/views.py
|
|
A question can be regraded for a given quiz.
Whole quiz can be regraded. Particular user paper can be regraded.
Moved validate_answer from views to models.
regrade method also updates the answer i.e. marks and correctness.
Also, the answer paper percentage is updated.
|
|
|
|
Stdin stdout evaluators
|
|
|
|
view_answerpaper
Resolved
Conflicts:
yaksh/views.py
|
|
|
|
|
|
|
|
After correct submission(POST) of code question, same question is shown for 2
seconds with a message "Correct Output".
After 2 seconds, the same correctly answered question is resubmitted(GET) to
the server.Since the question is already answered, it skips the question using
the skip method of answerpaper.
In skip method we have used cycle itertool, which loops in a cyclic
manner, never ending. So it is terminated when we get a question match
in an unanswered questions list with the submitted question. But the
question is already answered so we never get a match and loop runs
infinitely.
So used list instead of cycle.
Also, after correct answer, the user is to always get first question in
the answered list of question instead of next question after the
answered one.
So changed the completed_question method of answerpaper.
|
|
|
|
|
|
|
