Student Tracking

When you click into an assignment, you will see a table containing all the student you have sent the assignment to.

This table is broken into three different sections:

In Progress - Students who have been sent the assignment but have not yet started/finished.

Passed - Students who have passed the assignment.

Failed - Students who have failed the assignment.

An Activity Log is available for each student, which provides a real-time overview of how a student is progressing through your assignment. See the end of this page for more details.

In Progress

In the In Progress section, the Time Left initially shows how long the student has to complete the assignment (based on the Deadline value for your assignment).

There is also a Last Event column showing which step each student is at when taking one of your assignments. The full list of event types (and an explanation on when each is created) are given in the table below:

Event	Description
Sent Email	A student is initially sent an assignment.
Opened Email	A student opens the email that is sent to them containing the link to start their assignment.
Clicked Email	A student clicks the link to start their assignment.
Started	A student begins the assignment.
Pushed First Commit	A student pushes their first commit to the GitHub repo created for their assignment.
Completed	A student submits their solution to their assignment.
Email Bounced	When a email containing the link to start an assignment fails to send to a student. This happens when the recipient email address does not exist.

Passed and Failed

Both the Passed and Failed sections will contain a Score field, which is calculated as the number of passing unit tests ÷ number of total unit tests, given as a percentage. You can also sort the students by score.

The Failed section will also contain a Reason field, which will be one of the following values:

Reason	Description
Build Failure	Occurs when a student's solution fails to build/compile, preventing our analysis runner from advancing to the stage where it runs the automated tests.
Build Timeout	Occurs when a student's solution is running for more than one hour.
Unit Tests	Occurs when a student's solution fails to pass the required number of passing unit tests for your assignment.
Expired	Occurs when a student does not start your assignment before the assignment's Deadline, or starts the assignment but does not a push at least commit to their GitHub/GitLab repo before the assignment's Deadline.

You can then click the See Report button which will bring you to a screen containing the full report we generated for the student.

Activity Log

There is an Activity Log available for each student, which provides a real-time overview of how a student is progressing through your assignment. This makes it very easy for you to track student’s journeys through your assignments.