Development: Fix failing cypress tests that use sidebar

[muradium]

Checklist

General

• 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.

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 strictly followed the client coding and design guidelines.
• I documented the TypeScript code using JSDoc style.

Motivation and Context

Some tests fail after sidebar was introduced for exercise and lecture views.

Description

This PR adapts cypress e2e tests to new UI changes.

Steps for Testing

Run all cypress tests and confirm 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

Manual Tests

• Test 1
• Test 2

[coderabbitai]

Walkthrough

This update brings significant enhancements to the Cypress testing suite for a course management system, focusing on improving exercise filtering, navigation, and result verification functionalities. Changes include transitioning from ID to title-based exercise filtering, refining UI interaction methods, and enhancing assertion strategies to ensure more reliable and intuitive test flows.

Changes

Files	Summary
.../e2e/course/CourseExercise.cy.ts .../support/pageobjects/course/CourseOverviewPage.ts	Updated to filter and access exercises by title instead of ID.
.../e2e/exercises/ExerciseImport.cy.ts .../e2e/exercises/modeling/ModelingExerciseManagement.cy.ts .../e2e/exercises/quiz-exercise/QuizExerciseParticipation.cy.ts	Enhanced exercise overview navigation and verification.
.../support/pageobjects/course/CourseCommunication.ts	Improved message search functionality with updated selector.
.../support/pageobjects/exercises/ExerciseResultPage.ts	Refined score visibility check with more specific selector.

Possibly related issues

• Issue Key: Programming Exercise: Changing the short name while importing breaks tests #7188: The changes in exercise filtering and navigation might indirectly address the issue of test case functionality when the short name is changed, by improving test stability and reliability.
• Issue Key: Problem statement in the programming exercise detail page is not showing the template repo status correctly #7880: Although the PR does not directly address the template submission status display, the improved navigation and assertion methods could be adapted to enhance related test scenarios.
• Issue Key: Plagiarism, Programming Exercises: Side-by-side view incorrectly handles HTTP 409 responses from /api/repository/*/files #7026: Not directly related, but the focus on robust test assertions and navigation could indirectly benefit the handling and verification of error responses in similar contexts.
• Issue Key: Development: Course access authorization alert sometimes appears twice #6382: The enhancements in course exercise navigation and filtering may contribute to resolving issues related to course load and authorization checks, potentially mitigating the double alert problem.

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.