Feature/assessment/improve presentation UI

[jsuckart]

Summary

This PR is the second iteration of introducing presentation assessments to artemis. It reworks the database structure to support different grading instances for each presentation and improves the UI. Additionally it adds a feature toggle for the feature.

Checklist

General

• I tested all changes and their related features with all corresponding user types on a test server.
• This is a small issue that I tested locally and was confirmed by another developer on a test server.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Server

• Important: I implemented the changes with a very good performance and prevented too many (unnecessary) and too complex database calls.
• I strictly followed the principle of data economy for all database calls.
• I strictly followed the server coding and design guidelines and the REST API guidelines.
• I added multiple integration tests (Spring) related to the features (with a high test coverage).
• I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).

Client

• Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data (e.g. using paging).
• I strictly followed the principle of data economy for all client-server REST calls.
• I strictly followed the client coding guidelines.
• I strictly followed the AET UI-UX guidelines.
• Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
• I added multiple integration tests (Vitest) related to the features (with a high test coverage), while following the test guidelines.
• I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
• I added multiple screenshots/screencasts of my UI changes.
• I translated all newly inserted strings into English and German.

Motivation and Context

This PR adds the basis for presentation assessment.
This is intended as a minimal first iteration that establishes the backend domain, REST API, a prototype UI and a feature toggle, while keeping the implementation scoped and independent from the existing exercise assessment flow.

Description

The PR adds:

• A new presentation server package with domain, DTO, repository, service, and resource classes.
• A new presentation_assessment database table for course-level presentation assessments.
• A join table for assigning students to presentation assessments.
• REST endpoints under /api/courses/{courseId}/presentation-assessments.
• A new course setting presentationAssessmentsEnabled
• A Presentations sidebar entry below Lectures, only visible to instructors when enabled for the course.
• A presentation management UI with create/edit modal dialogs.
• Student assignment within the create/edit presentation modal.
• English and German translations for the new UI strings.

Steps for Testing

Prerequisites:

• 1 Instructor
• 2 Students
• 1 Course where the instructor has instructor permissions

1. Log in as an instructor.
2. Navigate to Course Administration.
3. Open the course settings.
4. Verify that the Presentations Enabled toggle is disabled by default.
5. Enable the toggle and save the course settings.
6. Verify that the Presentations entry appears in the course sidebar below Lectures.
7. Open Presentations.
8. Click Create presentation.
9. Enter a title, max points, optional result points, date, and description.
10. Add one or more students to the presentation.
11. Save the presentation.
12. Verify that the presentation appears in the table.
13. Edit the presentation and verify that the modal opens with the existing values and assigned students.
14. Change values and save.
15. Verify that the table reflects the updated presentation.
16. Delete the presentation and verify that it is removed from the table.
17. Go back to course settings, disable Presentations Enabled, save, and verify that the sidebar entry disappears.

Testserver States

You can manage test servers using Helios. Check environment statuses in the environment list. To deploy to a test server, go to the CI/CD page, find your PR or branch, and trigger the deployment.

Review Progress

Performance Review

• I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance even for very large courses with more than 2000 students.
• I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance even for very large courses with more than 2000 students.

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

Test Coverage

Note: Some tests in the Test job did not pass (failure). Coverage below may be partial.

Client

Coverage data not found. Run tests first or check if coverage-summary.json exists.

Server

Class/File	Line Coverage	Lines
DatabaseConfiguration.java	not found (modified)	24
Feature.java	not found (modified)	5
Course.java	not found (modified)	713
CourseCreateDTO.java	not found (modified)	66
CourseUpdateDTO.java	not found (modified)	90
ExerciseRepository.java	not found (modified)	623
PresentationAssessment.java	not found (modified)	98
PresentationAssessmentInstance.java	not found (modified)	95
PresentationAssessmentMode.java	not found (modified)	4
PresentationAssessmentDTO.java	not found (modified)	28
PresentationAssessmentInstanceDTO.java	not found (modified)	16
PresentationAssessmentStudentDTO.java	not found (modified)	11
PresentationAssessmentInstanceRepository.java	not found (modified)	16
PresentationAssessmentRepository.java	not found (modified)	40
PresentationAssessmentService.java	not found (modified)	152
PresentationAssessmentResource.java	not found (modified)	137

Last updated: 2026-08-24 12:33:33 UTC

Screenshots

[github-actions]

End-to-End Test Results

Phase	Status	Details
All Tests	✅ Passed	Tests Passed ✅ Skipped ⚠️ Failed Time ⏱ All E2E Tests Report (PR) 372 ran 365 passed 7 skipped 0 failed 45m 46s

Test Strategy: Running all tests (configuration or infrastructure changes detected)

Overall: ✅ E2E tests passed

🔗 Workflow Run · 📊 Test Report