Creating and publishing tests

Dashboard

This is your dashboard.

Creating a new test

To create a new test, follow these steps:

1. On the administrator dashboard, click Create New Test.
2. In the Search for skills field enter the name of the skill that you want to test the candidates in. 

Note: You can enter a maximum of 5 skills.            

3. Click the required skills for your test from the listed suggestions.
   
   

     

   Important: The skill list comprises major skills. If you want to test candidates on specific skills that do not exist in the list, then create the test manually.
   
   
4. Select the number of years of experience that is relevant to your requirement.

Note: By default, 0-3 years is selected. 

5. Click Next.

A summary of the new test will be displayed on the screen.

6. Click Create test.

 You have successfully created a new test.

Basic description

You can add information about your test.

Note: Instructions are populated by default, however, you can add your own instructions.

Question pooling

Question pooling is the process of adding questions from a question pool to a test that multiple candidates attempt such that each candidate receives a different set of questions.

You can create a question pool either from the questions in HackerEarth’s library or from those in your custom library (My Library).

For more information about creating a question pool, read this.   

Test settings

Test settings allow you to customize your test based on your requirements. For example, you can control the look and feel of your test, add multiple proctoring mechanisms, or restrict IP addresses from which the test can be taken.

Certain settings are applicable only to public tests.

The various settings that you can make in this section include the following:

Important: You must save individual test settings after you tailor the settings to meet your requirements.

Time settings

You can set the start and end dates, time, and test duration here. This section also allows you to disable or enable access to a test.

Question settings

In this section, you can enable settings to randomly shuffle all the questions in the test.

Note: The options in your MCQs will not be affected by this setting.

You can set a specific score for a test to filter candidates who score less than the score that you have set.

Note: A cut-off score is only an indication for you to filter candidates. HackerEarth Recruit does not automatically filter people who have scored less than the cut-off score that you have specified.

Candidate settings

This section allows you to select the details that you want the candidate to provide before starting the test. By default, Recruit provides a list of the most common details gathered by recruiters such as name, university name, years of experience, graduation year etc.

However, you can collect custom details from candidates. For example, you can use collect specific information about running the candidate’s code.

General test settings

You do not need to make any settings here.

This section is just for your information and provides the following:

• Test link: The long URL of your test.
• Short link: The short version of your test URL.
• Test ID for Recruiter API: This ID is used to define which test is used for actions like inviting candidates, viewing reports etc. when using HackerEarth Recruit’s APIs.

Report settings

This option is not selected by default. Select this option to receive a candidate report whenever a candidate takes your test.

Password settings

Important: These settings are applicable to public, password-protected tests only.

When you do not set a password for the test, anyone who has the link can access the test.

If you have chosen not to add a password to a test, you cannot add a password after the test is published.  

Proctoring settings

These settings enable you to supervise candidates during an online test. You can make various settings in this section such as confirming the identity of the candidate who is taking the test while ensuring the integrity of the test environment, force a candidate remain in the test environment, etc. to ensure that the test is fair for all candidates.

The various settings that you can make in this section include the following:

• Disable copy and paste in the code editor
  • The code editor is the text area where candidates write their code.
  • When this is setting is enabled, Ctrl+C and Ctrl+V are disabled in the code editor due to which candidates cannot copy from or paste in it.
• Disable copying of problem statement
  • Candidates will not be able to copy the problem statement from the test.
• Take candidate snapshot during the test
  • This setting takes a photograph of the candidate at random intervals.
  • When this setting is enabled, candidates will not be able to take the test if:
    • Computer does not have a working webcam
    • Webcam is not switched on
  • Restrict candidate to full-screen mode during the test
    • Candidates will be able to take the test in full-screen mode only.
    • If candidates exit the full-screen mode, a warning will be displayed on the screen. Once they exceed the number of warnings that you have specified in the proctoring settings, they will be logged out of the test.
  • Logout on leaving test environment
    • HackerEarth Recruit’s most stringent proctoring setting.
    • Candidates cannot leave the test screen.

Note: It is recommended that system updates are disabled before starting the test.

• Any popup or external click is counted as leaving test environment.
• You can set a minimum number of tab switches that is allowed.

Note: It is recommended that you keep a minimum of 5 tab switches.

Admins for this test

In this section, you can do the following:

• Add or remove administrators for the test
• Manage permissions that each administrator is given
• Set a point of contact whose email ID will be used to send emails to candidates and receive emails from candidates

Publishing tests

It is important that you publish your test. You can share the test link or invite candidates only after publishing the test.