How to give a Full Stack test

Full Stack Problem Workflow for Candidate 

1. Landing and Instruction Page for Candidate 

2. After starting the assessment and giving the declaration, the candidate will see the following page while attempting the full stack question.

3. The candidate must click the Create Workspace button so the VM gets ready. The candidate can read & understand the Problem Description in the time. On clicking the Create Workspace button, the page appear as follows:

4. It usually takes 3-7 minutes for the Workspace/VM to be ready. Once the Workspace/VM is ready, the page appears as follows:

5. The candidate has to click on the "Open IDE" button, which takes them to the IDE. 

6. The candidate can traverse the folder structure through the left sidebar, open the required files and start coding.

IDE features:

• Use the BUILD button to install the packages through NPM and run the application on PORT 8000. When the candidate hit this button for the first time, it will take time as all the required packages will be installed then.

• The candidate hit BUILD at least once before submitting to pass the test cases.

• The candidate can use the button PORT:8000 in the IDE to Live Preview the application. The Live Preview is opened on a new browser tab

• The candidate can use the TEST button to run the test cases available in the project folder.

• The candidate can use the SUBMIT SOLUTION to submit the entire solution for test-case evaluation and grading. The candidate will be assigned a score based on this.

7. Once the candidate has clicked the Submit Solution button, the following screen will appear:

8. Now the candidate's code is being evaluated. The evaluation usually takes 5-10 minutes. Once the evaluation is completed, the candidate will see the following change on the same page:

9. If the solution is correct and all test cases pass, it will be shown as if some test cases pass it will be shown as  & if no test case passes it will be shown as. The candidate can click on the Show Results button to check for the specific error messages of failed test cases.