Add setup files for e2e tests #534
Open
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
|
Hi @treoden, I've added the setup files for E2E tests. Please review them, so that I can continue adding the automated test scripts. |
|
Hi @ishabaral , Yes I see. Please give me sometime I will get back to you asap |
saw-jan
reviewed
May 17, 2024
|
Also, another thought, should the e2e tests be in the project root or in the packages/evershop package? |
added dotenv files used variables from .env set slowmo time to 0 cucumber config file edited
|
|
Hi @ishabaral , @saw-jan , I prefer the e2e be in the project root, not a part of evershop packages. Since it is for the core development only. |
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.
Added setup files for e2e testing utilizing Playwright and Cucumber.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The repository lacks end-to-end (E2E) testing. This means there are no automated tests in place to validate the application's functionality from end to end. As a result, there is a higher risk of undetected bugs and it becomes challenging to ensure the overall reliability and robustness of the application.
Issue Number: #532
What is the new behavior?
Added setup files for end-to-end (E2E) testing using Playwright and Cucumber which facilitates Behavior-Driven Development (BDD) practices. With this setup, we can define test scenarios in Gherkin language, ensuring comprehensive coverage of our application's behavior.
Does this PR introduce a breaking change?
Other information