First and foremost, we highly encourage your students to sign the CodeHS Honor Code. This will help set the tone for the rest of the year around what is acceptable and what is not. Creating a class culture of good digital citizenship and establishing ground rules can go a long way in preventing student cheating.

The Code History tab is a way for teachers and students to see all of the changes and revisions that have been made to a certain program. It is accessible on any code editor page under the More > History tab in the top right corner. You can use arrows to quickly move back and forth between timestamps of code.

Code History is a great tool to aid in cheat detection, as teachers can assume that exercises (particularly more complex exercises) which are completed quickly with very few code runs/saves are often attributable to borrowed or copied code. Teachers can also see the total time spent on an assignment from the Grade tab, located on the right side of the IDE. Check out Grading a Single Assignment to learn more!

Alternate exercises are different versions of existing assignments in CodeHS courses. These assignments are changed in subtle ways so that the core concept and difficulty are not altered, but a different autograded solution is required. You can switch out specific assignments in your course to help deter cheating. See Using Alternate Exercises to learn more!

On the Section Settings page, Pro teachers have access to three features that can help prevent student cheating:

Click the gear icon in the top-right corner of your roster page to access the Section Settings page:

Then, scroll to the bottom to find Advanced Settings:

This tool displays how long students have spent on an assignment. You can find the Time Tracking tool under the Progress view.

As soon as the Code Editor loads, time tracking begins for students. The tracker records every increment of 5 seconds that the student is active. Students become idle after 30 seconds of not moving their mouse or typing.