The upGrad learning platform features two main types of coding assessments: In-module coding questions and Timed assessments. In-module coding questions allow a learner to run, verify, and submit code at their own pace. On the other hand, timed assessments involve a strict time limit where the submit action is automatically triggered at the test conclusion. Evaluation criteria differ between these assessments as in-module questions focus on verification against both sample and non-sample test cases, while timed assessments primarily evaluate the ability to quickly produce correct code under time constraints .

During a timed assessment on the upGrad platform, students can initially use the 'Run' and 'Verify' options to check for errors and ensure all sample test cases pass. However, they must eventually rely on the 'Submit' feature, which is automatically triggered at the end of the timed period, to comprehensively assess their code against both sample and non-sample test cases. This setup encourages efficient time management and accuracy .

Omitting non-sample test cases from a coding assignment's evaluation on the upGrad platform would lead to a situation where the code remains in a 'submitted' state and is neither explicitly accepted nor rejected. This could potentially undermine the reliability of the evaluation process, as without the rigour of hidden non-sample test cases, it's possible for students to pass submissions through hardcoded scenarios optimized only for sample cases, thereby reducing the assessment's effectiveness in gauging true coding proficiency and adaptability .

The upGrad evaluation engine checks the correctness of submitted code in non-sample test cases by assessing it character by character at the backend. Even a single character mismatch can prevent the acceptance of expected output, emphasizing precision in coding. This stringent evaluation method compels students to ensure every detail of their code aligns perfectly with the expected output, promoting careful attention to detail .

The 'Submit' option in the upGrad coding console validates code against both sample and non-sample test cases. A code submission is accepted if it passes all of these test cases successfully. If non-sample test cases fail, the code is rejected, although partial marks may be granted depending on the number of passed non-sample test cases. This dual-layered testing ensures comprehensive evaluation of code correctness and robustness .

The upGrad platform facilitates iterative testing and improvement of code through features such as 'Run', 'Verify', and 'Submit'. The 'Run' option enables learners to check for syntactical and execution errors, providing a baseline for initial code debug. The 'Verify' option aids in checking code against sample test cases to verify logical correctness. Finally, the 'Submit' option allows testing against non-sample test cases for conclusive evaluation. This structured process encourages students to iteratively refine their code, building a deeper understanding of debugging, logic structuring, and problem-solving, critical to skill development .

The 'Run' feature in the upGrad coding assessments serves to identify syntactical, runtime, or execution errors in a learner's code. It provides an immediate check of code execution feasibility but does not evaluate the code against any test cases, either sample or non-sample. As a result, while it is useful for detecting errors, it has no direct impact on the actual assessment outcome which depends on the passing of test cases through the 'Verify' and 'Submit' features .

Sample test cases are visible to learners and serve as initial checks for the logic of their code, allowing modifications based on observed performance. Non-sample test cases, however, are hidden and are the primary determinant of the final score in the evaluation process, as they prevent learners from hard-coding solutions. Evaluation focuses on non-sample test cases to ensure that the submitted code is robust and generalizable to different inputs .

upGrad prevents hard-coding solutions by hiding the non-sample test cases to ensure learners can't tailor their solutions specifically to known inputs. The validity of code is evaluated by passing both sample and non-sample test cases, with the final score awarded solely based on non-sample test cases' success. This approach ensures that submitted solutions are generalizable rather than specifically tailored .

The submit-on-test-end approach in upGrad's timed assessments impacts a student's coding practice by imposing a time constraint that necessitates effective time management and prioritization of tasks. This method compels students to balance the depth of their solution with the time available, encouraging the development of quick problem-solving skills and the ability to write functional code under pressure. It further emphasizes the importance of having a strategic approach to assessments, potentially influencing how students prepare and practice coding outside of test conditions .