INGInious
stable
  • Installation, configuration and upgrade
  • Commands reference
  • Teacher’s documentation
    • What is INGInious?
    • Creating a new course
    • Creating a new task
      • Tutorial
      • Task reference
      • Allowing students to download files
      • Overriding system files
      • Debugging tasks
      • Unit-tests on tasks
      • Best practices
    • Creating a new container image
    • Course administration
    • Batch containers
  • 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
  • Task reference
    • Task description files
    • Run file
  • Allowing students to download files
  • Overriding system files
  • Debugging tasks
    • Debug information
    • SSH debug
  • Unit-tests on tasks
    • Defining a new unit test
    • Creating a new test file
    • Generated test files
    • Automated tests with *.test files
  • 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-2017, the INGInious authors. Revision eb019713.

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