Set Up Automated Testing with Playwright #688
Merged
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
xannyxs
force-pushed
the
playwright-frontend-tests
branch
from
34c1be5 to
9bb79b1
Compare
Closed
23 tasks
xannyxs
changed the title
Mario-SO
approved these changes
Aug 12, 2024
greatsamist
pushed a commit
that referenced
this pull request
Aug 13, 2024
## Description This PR introduces the foundation for our automated end-to-end (E2E) testing suite using `playwright`. We've implemented initial test scenarios covering critical user flows across three key areas of our application. ### Test Scenarios Implemented: 1. **Legal Pages** - Verify page titles - Confirm page existence 2. **Login Page** - Ensure login page loads correctly - Validate successful login functionality 3. **Create Organization Page** - Test creation with mandatory information only - Test creation with mandatory information and description - Validate handling of missing inputs - Verify responses to incorrect inputs ### Technical Details: - Framework: Playwright - Browsers Tested: Chromium, Firefox ## Type of Change - [x] New feature (non-breaking change which adds functionality) - [x] This change requires a documentation update ## Impact This change lays the groundwork for comprehensive automated testing, which will: - Improve code quality and reliability - Accelerate the development process by catching issues early - Enhance confidence in deployments ## Additional Context Documentation on the testing framework, including how to start the tester locally, add new tests and best practices, will be added to the StreamETH Notion. This will serve as a guide for current and future developers to understand and expand our testing suite.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR introduces the foundation for our automated end-to-end (E2E) testing suite using
playwright. We've implemented initial test scenarios covering critical user flows across three key areas of our application.Test Scenarios Implemented:
Legal Pages
Login Page
Create Organization Page
Technical Details:
Type of Change
Impact
This change lays the groundwork for comprehensive automated testing, which will:
Additional Context
Documentation on the testing framework, including how to start the tester locally, add new tests and best practices, will be added to the StreamETH Notion. This will serve as a guide for current and future developers to understand and expand our testing suite.