Skip to content
English
  • There are no suggestions because the search field is empty.

How the Autograder Works

In this article, you will learn how the autograder works and goes over the different types of autograders used in Skill Struck.

Last updated - October 1, 2025

 

Each challenge and checkpoint has a specific output or set of requirements it is looking for. There are two types of autograders used in Skill Struck, requirement-based and input/output-based. Requirement-based activities have a list of requirements that must be met for a student to pass. Input/output-based activities look for a specific output.

 

Requirement-Based

The requirement-based autograder is the most commonly used autograder type. This autograder will have a list of requirements in the bottom left corner of the screen. Each requirement must be met in order for students to pass this type of activity. Requirement-based activities look for specific syntax to be used, so attention to detail is paramount for this autograder type. 

requirements autograder 1

 

 

Input/Output-Based

The input/output-based autograder only looks for a specific output. The code used to get that output doesn't matter. This style allows students to think creatively and solve coding problems in a variety of ways. Since students aren't working from a checklist of requirements, they will need to apply problem solving skills to solve each problem and pass each activity. 

input-output autograder 1

 

 

Autograder Tips

  • Each challenge will include the autograder type at the top of every vcheckpoint and challenge.
  • Challenges also include autograder tips that will help students align their code with the autograder for that challenge.
  • Before starting an activity, read the full instructions to get an understanding of what the autograder is looking for.
  • Remember that coding is specific. Make sure all code has correct spelling, syntax, and spacing.
  • Just because code successfully runs in the terminal does not mean that it meets the requirements of the activity.
  • When incorrect code is submitted, a hint will be provided. The hint will state a possible issue with the code, but may not state the exact problem.
  • Check your code, double-check, and check again! If submitted code is not passing, look it over for bugs. A bug can be as small as a missing semi-colon, a misspelled word, or an extra letter typed where it shouldn't be.
  • NOTE: When the instructions include red text, students must include this text in their code to pass.
    •  For example, if the instructions say, "include the word strawberry in a paragraph tag," the student's code should look something like this <p>strawberry</p>. Excluding the word strawberry would prevent this code from passing. 
    • Red words or phrases must be added in English regardless of the language used on the account.


If a student is having a difficult time passing an activity, you can manually give them credit in your Educator Portal. Click here for an article on how to do that.