Development: Remove redundant e2e test

[muradium]

Checklist

General

• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Client

• I strictly followed the client coding and design guidelines.
• I documented the TypeScript code using JSDoc style.

Motivation and Context

Changing the individual working time of test runs of a test exam did not make sense and have been changed to not be possible. This PR removes a corresponding E2E test testing this user flow.

Description

Removes the E2E test that tests the change of working time of an individual test run of a test exam.

Steps for Testing

• Code Review: Ensure that tests pass for valid reasons, functionality is adequately tested and check the code quality.
• Run the tests (optional): Tests are checked by automatic run in CI environment. You can optionally run them locally and check if they pass.

Testserver States

Note

These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Code Review

• Code Review 1
• Code Review 2

Summary by CodeRabbit

• Bug Fixes
  • Removed a test case related to changing the working time of a test run to streamline the test suite.
• Tests
  • Maintained existing tests for creating, conducting, and deleting test runs to ensure overall functionality remains intact.

[coderabbitai]

Walkthrough

The pull request involves a modification to the Playwright e2e test suite for exam test runs. Specifically, a test case responsible for changing the working time of a test run has been removed from the TestExamTestRun.spec.ts file. The removal does not appear to impact the overall structure or core functionality of the test suite, which continues to cover creating, conducting, and deleting test runs.

Changes

File	Change Summary
src/test/playwright/e2e/exam/test-exam/TestExamTestRun.spec.ts	Removed a test case for changing working time of a test run, which previously included steps for login, test run creation, working time modification, and verification

Sequence Diagram

sequenceDiagram
    participant Instructor
    participant TestRunPage
    participant TestRun

    Instructor->>TestRunPage: Navigate to test run
    Instructor->>TestRun: Modify working time (previously)
    TestRun-->>TestRunPage: Update confirmation

Loading

Possibly related PRs

• Development: Add e2e playwright tests for exam announcement #8630: E2E tests for exam announcements with working time functionality
• Development: Fix flaky playwright e2e tests involving automatic exercise assessments #8740: Refactoring of ExamResults.spec.ts
• Development: Fix and re-enable exam mode e2e tests #8946: Addressing exam mode test issues
• Development: Fix exam assessment e2e tests failing #9462: Fixing exam assessment issues
• Development: Fix exam results overview e2e test #9472: Modifying student exam retrieval logic
• Development: Add exercise update announcement e2e tests #9784: E2E tests for exercise updates
• Development: Add e2e tests for instructors assessing exams in the second round #9863: E2E tests for instructor exam assessment

Suggested labels

tests, ready to merge, chore

Suggested reviewers

• SimonEntholzer
• krusche
• az108

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d10a20c and b0978e1.

📒 Files selected for processing (1)

• src/test/playwright/e2e/exam/test-exam/TestExamTestRun.spec.ts (0 hunks)

💤 Files with no reviewable changes (1)

• src/test/playwright/e2e/exam/test-exam/TestExamTestRun.spec.ts

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.