Content of this document
Conducting a programming exercise consists of 7 steps distributed among instructor, Artemis and students:
- Instructor prepares exercise: Set up a repository containing the exercise code and test cases, build instructions on the CI server, and configures the exercise in Artemis.
- Student starts exercise: Click on start exercise on Artemis which automatically generates a copy of the repository with the exercise code and configures a build plan accordingly.
- Optional: Student clones repository: Clone the personalized repository from the remote VCS to the local machine.
- Student solves exercise: Solve the exercise with an IDE of choice on the local computer or in the online editor.
- Student uploads solution: Upload changes of the source code to the VCS by committing and pushing them to the remote server (or by clicking submit in the online editor).
- CI server verifies solution: verify the student’s submission by executing the test cases (see step 1) and provide feedback which parts are correct or wrong.
- Student reviews personal result: Reviews build result and feedback using Artemis. In case of a failed build, reattempt to solve the exercise (step 4).
- Instructor reviews course results: Review overall results of all students, and react to common errors and problems.
The following activity diagram shows this exercise workflow.
The following sections describe the supported features and the process of creating a new programming exercise.
The following screenshot shows the online code editor with interactive and dynamic exercise instructions on the right side. Tasks and UML diagram elements are referenced by test cases and update their color from red to green after students submit a new version and all test cases associated with a task or diagram element pass. This allows the students to immediately recognize which tasks are already fulfilled and is particularly helpful for programming beginners.
Display of hidden files
The online editor displays only visible files, to avoid showing for example .git and .gitignore config files. This also means that other config files, like SwiftLint's .swiftlint.yml file, are not shown. Those files currently can only be accessed via your own IDE.
Artemis Java Test Sandbox (abbr. AJTS) is a JUnit 5 extension for easy and secure Java testing on Artemis.
Its main features are
- a security manager to prevent students crashing the tests or cheating
- more robust tests and builds due to limits on time, threads and io
- support for public and hidden Artemis tests, where hidden ones obey a custom deadline
- utilities for improved feedback in Artemis like processing multiline error messages or pointing to a possible location that caused an Exception
- utilities to test exercises using System.out and System.in comfortably
For more information see https://github.com/ls1intum/artemis-java-test-sandbox