Checklist

General

• I tested all changes and their related features with all corresponding user types 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) database calls.
• I followed the coding and design 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).
• I documented the Java code using JavaDoc style.

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.
• I followed the coding and design 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 (Jest) 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 documented the TypeScript code using JSDoc style.
• I added multiple screenshots/screencasts of my UI changes.
• I translated all newly inserted strings into English and German.

Changes affecting Programming Exercises

• I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
• I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).

Motivation and Context

There are many problems that can occur during the exam. Many are hard to predict and even harder to fix in a timely manner. An example is an unexpected problem with artemis related servers.

Therefore, we need a feature to extend the working time.

Close #7045

Description

This PR adds a new button "Edit Exam Duration" to the exam summary page. When clicking, a dialog opens, which allows to edit the exam duration by adding time to it. After verifying with the exam name, and clicking "Change", the exam working time is updated.

Steps for Testing

Prerequisites:

• 1 Instructor
• 2 Students
• 1 Exam w/ Programming exercises

Steps:

1. Log in to Artemis
2. Navigate to Course Administration
3. Navigate to Exams
4. Create an Exam
5. Add a programming exercise to the exam
6. Add students to the exam
7. Start the exam
8. While the exam is running, use the new Edit Exam Duration button to extend the working time
9. Edit the time by which the exam deadline should be extended
10. Enter the name of the exam
11. Hit the "Change" Button

Outcome:

• The working time update should be reflected in the exam summary view
• The working time should update for all participating students
• The programming exercise repositories should not lock at the original end time
• The programming exercise repositories should lock at the updated end time

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
• I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

Exam Mode Test

• Test 1
• Test 2

Test Coverage

Screenshots

Button disabled if close to submission

Update working time