CodeEval - Hands On Guidelines

Download as pdf or txt
Download as pdf or txt
You are on page 1of 3

Code Eval Walkthrough

Whenever there is an assessment (technical or aptitude), it is mandatory to know the platform better.
Reading the instructions, before the test will help understand the scoring schema (negative
marking/sectional cut off/weightage), time allotted for the test, hovering/moving to the other
sections/questions, submission guidelines, auto or manual submission, etc.
When a test is started in CodeEval, the screen would be like:

[email protected]
D0OLHR8SGA

The default view of the compiler can change based on the proctoring/AI proctoring based choices.

The platform intends to check your logical and problem solving abilities. It is not an online IDE, where the
platform lets you go with any different programs. It is a dedicated assessment platform, where the
response is checked against the default test cases and grades your submission. Please read the document
clearly, this document aims to clear the doubts you may have, since you are moving to an online
assessment platform from an offline IDE.

This file is meant for personal use by [email protected] only.


Sharing or publishing the contents in part or full is liable for legal action.
Know the CodeEval Platform:

1. In the main screen, there would be 2 option tabs. The Problem Statement tab would contain
the question, Input Format (optional), Output Format (optional), Input Constraint (optional),
Sample Input and Output (Optional). The question can be a 2 liner or a story based problem
[email protected]
D0OLHR8SGA
statement, but it is mandatory to have a clear picture about the same.
2. The second tab after the Problem Statement tab would be the Test cases tab. The test cases tab
would contain Hidden and Visible Test cases, and the weightages of the test cases also. The
hidden test cases cannot be seen at any cost. Please find the screenshot below.
3. Topic Help - This area provides you with the conceptual notes on the problem at hand.
4. The Work Area tab would let the user write the code for the given problem statement. The
Work Area tab would contain the pre-written code too. At any cost, the pre-written code is not
to adjusted or altered.
5. AI tutor - The AI tutor can help guide you towards the right answer. It will evaluate your code
and suggest hints to improve it and drive you towards the right answer.
6. Test Program - This tab will let you know the number of test cases your program has passed.
Once when the program is ready to be evaluated, click on Test Code Button). Please note the
Test Code Button doesn’t ensure submission. The Test Code button evaluates the user code
against the Test cases and would show the Test case Evaluation Section.

7. On completion, the test must be submitted using the Submit button. The responses get

This file is meant for personal use by [email protected] only.


Sharing or publishing the contents in part or full is liable for legal action.
captured only when the test is submitted. When the test runs out of the time, it is
considered improper submission. It is mandatory for the user to submit the test.
8. Input information or output information statement must not be present, unless the question
demands to. For example,

The output statements like (in Python):


n = input(“Enter the string”)

should not be present, in the code, unless the question asks you to.

The platform is user-friendly and suggests for auto-filling as well. If the output is not expected or
if there is an improper submission, it is hardly the mistake of the compiler. Please align or
modify the code according to the expected output.

-----------------------------------Happy Coding!!!--------------------------------------------

[email protected]
D0OLHR8SGA

This file is meant for personal use by [email protected] only.


Sharing or publishing the contents in part or full is liable for legal action.

You might also like