-
Notifications
You must be signed in to change notification settings - Fork 73
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
feat: E2E test using Playwright #2115
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gee05053
force-pushed
the
feat/e2eTesting-playwright
branch
from
January 21, 2024 07:22
9f747b6
to
f96cb1f
Compare
yomybaby
requested changes
Feb 5, 2024
Coverage report for
|
St.❔ |
Category | Percentage | Covered / Total |
---|---|---|---|
🔴 | Statements | 3.02% | 102/3378 |
🔴 | Branches | 3.19% | 69/2165 |
🔴 | Functions | 1.5% | 17/1133 |
🔴 | Lines | 3.08% | 102/3315 |
Test suite run success
20 tests passing in 4 suites.
Report generated by 🧪jest coverage report action from 278c09f
yomybaby
requested changes
Feb 19, 2024
yomybaby
added a commit
that referenced
this pull request
Aug 22, 2024
…2647) > [!NOTE] > This PR is newly written referring to #2115 ### TL;DR Added end-to-end testing setup using Playwright ### What changed? - Installed Playwright as a dev dependency - Added Playwright configuration file (playwright.config.ts) - Created initial end-to-end tests for login functionality and virtual folder operations - Updated .gitignore to exclude Playwright-related files and directories - Added a data-testid attribute to the user dropdown button for easier test selection ### How to test? 1. Install dependencies: `pnpm install` 2. Run the application locally 3. Execute the tests: `npx playwright test` 4. View the test results in the console or generated HTML report ### Why make this change? Implementing end-to-end tests helps ensure the application's critical paths function correctly from a user's perspective. This addition will improve the overall quality and reliability of the project by catching potential issues early in the development process and providing confidence during future changes or refactoring.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
effort:normal
Need to understand a few modules / some extent of contextual or historical information.
size:XL
500~ LoC
type:enhance
Add new features
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR resolves #2081
Implement e2e test using playwright
Loop Doc
You must make .env file at playwright directory(webui/playwright/.env) and copy and paste below config
How to run
Checklist: (if applicable)