-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BD-26][EDUCATOR-5761, EDUCATOR-5762] Add additional pages for proctored exams #10
[BD-26][EDUCATOR-5761, EDUCATOR-5762] Add additional pages for proctored exams #10
Conversation
…ngs and instructions
…ng exam instructions (#14) Co-authored-by: Ihor Romaniuk <[email protected]> Co-authored-by: Sagirov Evgeniy <[email protected]>
…#16) * feat: Cover timed exam functionality with unit and functional tests
… and support for js workers from provider (#20) * feat: add handling of exam API errors * feat: add support for workers from proctoring providers
…ding on the frontend
Thanks for the pull request, @viktorrusakov! I've created BLENDED-855 to keep track of it in Jira. More details are on the BD-26 project page. When this pull request is ready, tag your edX technical lead. |
can you update this with the commits from |
c74970c
to
c51257b
Compare
@zacharis278 review please, this one should be merged first |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new views themselves look good but there's a few things I noticed while going through the code.
- It seems like we're doubling up API calls to the backend for review policy and settings (it's not just OPTIONS requests but multiple GETS)
- If the settings call fails I seem to get an infinite loading animation. (this can definitely be fixed in another PR)
- I'm going to take a detailed look at the tests later for what's important but based on codecov it seems like our coverage is lacking.
@@ -168,7 +175,7 @@ export function stopExam() { | |||
}; | |||
} | |||
|
|||
export function continueExam() { | |||
export function continueExam(noLoading = true) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is mostly a comment on the existing code here. This continue exam flow isn't making much sense to me, why do we need to make a backend call with a start
action?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is mainly used when you are on ready_to_submit page and instead of clicking 'submit' you click 'continue my exam', then this function gets called (this is also how it is done in LMS)
Also in this PR this function is used to start proctored exam (I'm not sure why I did this) but it gets refactored in #14
@@ -9,6 +9,7 @@ export const examSlice = createSlice({ | |||
activeAttempt: null, | |||
proctoringSettings: {}, | |||
exam: {}, | |||
verification: {}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would be nice to scaffold out the entire model for each of these backend models so developers know what the data will look like. (proctoringSettings, exam, verification)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will create tests for redux later and I believe we will have snapshots / factories for our data, will it work or do you mean something else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd hoped to see something more like this for each model
verification: {
status: '',
can_verify: false,
},
...
let's follow up in another PR since I've merged this already.
|
I'm going to go ahead and merge this in and keep track of things we may need to fix as we go |
🎉 This PR is included in version 1.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This PR adds following pages for proctoring exam flow: user verification, system check, ready to start instructions
NOTE: should be merged first
JIRA: EDUCATOR-5761 EDUCATOR-5762