Open John-Paul-Larkin opened 12 hours ago
Hello I would be happy to jump on writing any one of these tests for you. I guess I will start by jumping on the first one: 1. Profile Picture Upload
I'll let you know if I come across any questions, but it seems pretty straight forward. 👍🏻
Awesome. Thanks @petercr
Context
We need to ensure that our core application features and user flows are fully covered by end-to-end (E2E) tests. We are using Playwright for these tests, and the workflow framework for E2E testing is already in place.
If you navigate to the e2e folder in the root of the project, you'll find that @JohnAllenTech has written numerous tests for the article page. These tests have been grouped into two categories: authenticated and unauthenticated. Please ensure that this pattern is followed when adding new tests.
Expected Behavior
Below is a list of possible tests for the
/settings
page. These are suggested tests generated with the help of ChatGPT, meant to provide a starting point. You should use your discretion to refine these tests and account for relevant edge cases. Ensure that tests for each input field align with the current Zod validation schema.Additionally, feel free to propose other valid tests that might apply specifically to the functionality of the settings page.
Tests should be standalone and focus on a single purpose, ensuring each test verifies only one specific behavior or functionality.
Test should be added to e2e/settings.spec.ts
Please leave a comment specifying the tests you plan to write, so others don't duplicate the same efforts. All PRs are accepted for Hacktoberfest.
Note: For this page, the unauthenticated test is only necessary to verify that the user is correctly redirected to the
/get-started
page.Note: As multiple people may contribute to this issue, please ensure you pull the latest changes from the upstream and resolve any conflicts. Sync the upstream
Tests
Screenshots