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

test(e2e): add statisic UI e2e test #78

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

Conversation

zzcr
Copy link
Member

@zzcr zzcr commented Oct 11, 2024

PR

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our Commit Message Guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • Tests
    • Introduced a new test suite for the statistic component to capture UI screenshots across different states.

Copy link

coderabbitai bot commented Oct 11, 2024

Walkthrough

This pull request introduces a new test suite for the statistic component using Playwright. It includes three tests that capture UI screenshots for various states of the component. Each test sets up an error handler, navigates to specific sections of the component, checks the visibility of demo elements, and captures screenshots, saving them with designated filenames.

Changes

File Change Summary
tests/statistic/xdesign.spec.ts Introduced a new test suite for the statistic component with three tests for UI screenshot capture.

Possibly related PRs

  • test: add milestone UI e2e test #44: The milestone UI e2e test introduces a test suite that captures UI screenshots for the milestone component, similar to the screenshot tests for the statistic component in the main PR.
  • test(e2e): add collapse UI e2e test #69: The collapse UI e2e test includes tests that capture screenshots for different states of the collapse component, paralleling the screenshot functionality in the main PR's tests for the statistic component.
  • test(e2e): add guide UI e2e test #70: The guide UI e2e test captures screenshots for the guide component, aligning with the main PR's focus on UI screenshot testing for the statistic component.
  • test(e2e): add breadcrumb UI e2e test #71: The breadcrumb UI e2e test captures screenshots for the breadcrumb component, which is related to the main PR's emphasis on UI screenshot tests for the statistic component.
  • test(e2e): add ip-address UI e2e test #72: The IP address UI e2e test captures screenshots for the IP address component, reflecting the same testing approach as the main PR's screenshot tests for the statistic component.

Suggested labels

e2e

🐇 In the meadow, bright and spry,
New tests for statistic fly!
With screenshots clear, they dance and play,
Ensuring all's well, come what may.
Hopping through states, with joy we cheer,
For every capture, our vision is clear! 🌼


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>, 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 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 anywhere in the PR title to generate the title automatically.

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

@github-actions github-actions bot added the e2e playwright label Oct 11, 2024
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: 1

🧹 Outside diff range and nitpick comments (4)
tests/statistic/xdesign.spec.ts (4)

1-3: Consider using English for the test suite name.

The test suite name is currently in Chinese. For better internationalization and consistency across the codebase, consider using English for the test suite name.

Suggested change:

-test.describe('statistic组件xdesign规范', () => {
+test.describe('Statistic Component XDesign Specification', () => {

4-10: Approve test structure and suggest using English for the test name.

The test structure is well-organized and follows good practices. The error handler is a valuable addition to catch unexpected errors. However, consider using English for the test name to improve internationalization and consistency.

Suggested change:

-  test('默认--UI截图', async ({ page }) => {
+  test('Default - UI Screenshot', async ({ page }) => {

12-18: Approve test structure and suggest using English for the test name.

The test structure is consistent with the previous test, which is good for maintainability. However, consider using English for the test name to improve internationalization and consistency.

Suggested change:

-  test('前后缀--UI截图', async ({ page }) => {
+  test('Prefix and Suffix - UI Screenshot', async ({ page }) => {

20-26: Approve test structure and suggest using English for the test name.

The test structure remains consistent with the previous tests, which is good for maintainability. However, consider using English for the test name to improve internationalization and consistency.

Suggested change:

-  test('标题--UI截图', async ({ page }) => {
+  test('Title - UI Screenshot', async ({ page }) => {
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 0ea1f51 and 5b2d661.

⛔ Files ignored due to path filters (3)
  • tests/statistic/xdesign.spec.ts-snapshots/basic-usage-chromium-win32.png is excluded by !**/*.png
  • tests/statistic/xdesign.spec.ts-snapshots/prefix-suffix-slot-chromium-win32.png is excluded by !**/*.png
  • tests/statistic/xdesign.spec.ts-snapshots/statistic-slot-chromium-win32.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • tests/statistic/xdesign.spec.ts (1 hunks)
🧰 Additional context used

Comment on lines +1 to +27
import { expect, test } from '@playwright/test'

test.describe('statistic组件xdesign规范', () => {
test('默认--UI截图', async ({ page }) => {
page.on('pageerror', (exception) => expect(exception).toBeNull())
await page.goto('statistic#basic-usage')
const demo = page.locator('#basic-usage .pc-demo')
await expect(demo).toBeInViewport()
await expect(demo).toHaveScreenshot('basic-usage.png')
})

test('前后缀--UI截图', async ({ page }) => {
page.on('pageerror', (exception) => expect(exception).toBeNull())
await page.goto('statistic#prefix-suffix-slot')
const demo = page.locator('#prefix-suffix-slot .pc-demo')
await expect(demo).toBeInViewport()
await expect(demo).toHaveScreenshot('prefix-suffix-slot.png')
})

test('标题--UI截图', async ({ page }) => {
page.on('pageerror', (exception) => expect(exception).toBeNull())
await page.goto('statistic#statistic-slot')
const demo = page.locator('#statistic-slot .pc-demo')
await expect(demo).toBeInViewport()
await expect(demo).toHaveScreenshot('statistic-slot.png')
})
})
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Consider refactoring to reduce code duplication.

All three tests follow the same pattern, which presents an opportunity for refactoring to reduce code duplication and improve maintainability.

Consider creating a helper function to encapsulate the common test logic. Here's a suggested refactor:

import { expect, test } from '@playwright/test'

function testStatisticScreenshot(name: string, anchor: string, filename: string) {
  test(`${name} - UI Screenshot`, async ({ page }) => {
    page.on('pageerror', (exception) => expect(exception).toBeNull())
    await page.goto(`statistic#${anchor}`)
    const demo = page.locator(`#${anchor} .pc-demo`)
    await expect(demo).toBeInViewport()
    await expect(demo).toHaveScreenshot(filename)
  })
}

test.describe('Statistic Component XDesign Specification', () => {
  testStatisticScreenshot('Default', 'basic-usage', 'basic-usage.png')
  testStatisticScreenshot('Prefix and Suffix', 'prefix-suffix-slot', 'prefix-suffix-slot.png')
  testStatisticScreenshot('Title', 'statistic-slot', 'statistic-slot.png')
})

This refactoring reduces code duplication, improves maintainability, and makes it easier to add new test cases in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e2e playwright
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant