INGInious
v0.5
  • Installation, configuration and upgrade
  • Commands reference
  • Teacher’s documentation
    • What is INGInious?
    • Creating a new course
    • Creating a new task
      • Tutorial
      • Run file
      • Task description files
      • Allowing students to download files
      • Share common files between tasks
      • Random tasks parameters
      • Overriding system files
      • Debugging tasks
      • Best practices
    • Translating tasks
    • Creating a new container image
    • Course administration
    • Using through LTI (edX, Moodle, …)
  • Developer’s documentation
INGInious
  • Docs »
  • Teacher’s documentation »
  • Creating a new task
  • Edit on GitHub

Creating a new task¶

  • Tutorial
    • Creating the task description
    • Creating the run file
  • Run file
    • Feedback commands
    • reStructuredText helper commands
    • Input commands
    • run_student
    • archive
  • Task description files
    • Problem types
  • Allowing students to download files
  • Share common files between tasks
  • Random tasks parameters
    • Accessing the task random parameters
  • Overriding system files
  • Debugging tasks
    • Debug information
    • SSH debug
  • Best practices
    • Use YAML with RST
    • Provide a test set for the student to test their code themselves, and grade the code with at least this set
    • Do not use the “file” subproblem type
    • If you still have to use a “file” subproblem type, make it lightweight
    • If you still have to use a lightweight “file” subproblem, ask for code, not for binary executables
    • Do not delete tasks
    • Do not put the student’s code directly in your tests
    • Use student container
    • Make small tests
Next Previous

© Copyright 2014-2018, the INGInious authors Revision 72fbf3d5.

Built with Sphinx using a theme provided by Read the Docs.