Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development: Add e2e playwright tests for exam announcement #8630

Merged
merged 10 commits into from
May 25, 2024

Conversation

muradium
Copy link
Contributor

@muradium muradium commented May 18, 2024

Checklist

General

Client

Motivation and Context

We want to test exam announcement dialogs popping up by actions such as instructor sending a message or exam working time change.

Description

Adds E2E tests in Playwright about exam announcements.

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.

Steps for running the tests:

  1. Navigate to src/tests/playwright
  2. Configure Playwright using playwright.env file based on your local setup. Current configuration should work for default Artemis setup.
  3. Run npm install && npm run playwright:setup && npx playwright test e2e/exam/ExamParticipation.spec.ts
  4. Confirm that "Exam announcement" tests 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

@muradium muradium requested a review from a team as a code owner May 18, 2024 22:35
@github-actions github-actions bot added tests client Pull requests that update TypeScript code. (Added Automatically!) labels May 18, 2024
Copy link

coderabbitai bot commented May 18, 2024

Walkthrough

The recent updates primarily focus on enhancing the Playwright test suite for exam-related functionalities. Key changes include renaming the ExamParticipation class to ExamParticipationPage for consistency, adding unique IDs to button elements in HTML files, and introducing new classes and methods to manage exam announcements, working times, and modal dialog interactions. These improvements aim to streamline test scripts and enhance the clarity and maintainability of the codebase.

Changes

File Path Change Summary
src/main/webapp/.../exam-live-announcement-create-button.component.html Added id="announcement-create-button" to the button element.
src/main/webapp/.../exam-edit-working-time.component.html Added unique id attribute edit-working-time-button to the button element.
src/test/playwright/.../ExamAssessment.spec.ts Renamed ExamParticipation to ExamParticipationPage for consistency.
src/test/playwright/.../ExamParticipation.spec.ts Added ExamStartEndPage, Commands, ExamAPIRequests, ModalDialogBox, ExamParticipationActions, and createExam function.
src/test/playwright/.../ExamResults.spec.ts Renamed ExamParticipation to ExamParticipationPage for consistency.
src/test/playwright/.../TestExamStudentExams.spec.ts Renamed ExamParticipation to ExamParticipationPage for consistency.
src/test/playwright/support/fixtures.ts Renamed ExamParticipation to ExamParticipationPage, added ModalDialogBox and ExamParticipationActions imports, and updated references.
src/test/playwright/.../ExamManagementPage.ts Added imports for Dayjs and methods for managing announcements and working times.
src/test/playwright/.../ExamParticipationActions.ts Introduced ExamParticipationActions class with methods for interacting with exam participation actions.
src/test/playwright/.../ExamParticipationPage.ts Refactored ExamParticipation to extend ExamParticipationActions and removed unused methods.
src/test/playwright/.../ModalDialogBox.ts Added ModalDialogBox class for interacting with modal dialog boxes in tests.

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

coderabbitai[bot]
coderabbitai bot previously approved these changes May 18, 2024
rstief
rstief previously approved these changes May 23, 2024
Copy link
Contributor

@rstief rstief left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Demonstrated in testing session, Code also LGTM

Comment on lines +43 to +53
async checkExamFinishedTitle(title: string) {
await expect(this.page.locator('#exam-finished-title')).toContainText(title, { timeout: 40000 });
}

async checkExamFullnameInputExists() {
await expect(this.page.locator('#fullname')).toBeVisible({ timeout: 30000 });
}

async checkYourFullname(name: string) {
await expect(this.page.locator('#your-name')).toContainText(name, { timeout: 30000 });
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are the timeouts so long? This would be 40/30 seconds, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked and turns out these are timeouts for waiting for an exam to finish, delegated to POM functions. Would be better to wait for exam finish explicitly in the test if needed, not in an assertion coming after.

But these functions are not relevant to current PR, I just moved them to different POM. Maybe I should fix that in another PR?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, please fix it in another PR

BBesrour
BBesrour previously approved these changes May 23, 2024
Copy link
Member

@BBesrour BBesrour left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Demonstrated in a testing session.

@muradium muradium dismissed stale reviews from BBesrour, rstief, and coderabbitai[bot] via ffcdb3a May 23, 2024 13:25
Copy link
Member

@BBesrour BBesrour left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

re-approve

Copy link
Member

@BBesrour BBesrour left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

re-approve
(last one was a misclick :'))

Copy link
Contributor

@coolchock coolchock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

demonstrated in the testing session, looks good. I think you could also add another e2e test for problem statement updates in a follow-up PR.

@krusche krusche changed the title Development: Exam announcement e2e tests Development: Add e2e playwright tests for exam announcement May 25, 2024
@krusche krusche added this to the 7.1.0 milestone May 25, 2024
@krusche krusche merged commit 5cb587e into develop May 25, 2024
35 of 36 checks passed
@krusche krusche deleted the feature/playwright/exam-working-time-change branch May 25, 2024 20:18
@coderabbitai coderabbitai bot mentioned this pull request Sep 29, 2024
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client Pull requests that update TypeScript code. (Added Automatically!) ready to merge tests
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

6 participants