Add e2e tests for admin login feature#564
Open
prashant-gurung899 wants to merge 19 commits into
Open
Conversation
added dotenv files used variables from .env set slowmo time to 0 cucumber config file edited
Added setup files for testing
Set-up github actions
Setup github actions-CI
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 e2e tests using Cucumber(Gherkin Syntax) and Playwright browser automation tool to test admin login feature.
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?
Currently, Evershop hasn't implemented any testing(e2e-end to end). There are no tests to validate the expected behaviour of Evershop.
Manual testing is required to verify the functionality, which is time-consuming and prone to human error.
Issue Number: #532
What is the new behavior?
Added test scenarios in Gherkin Language for e2e test of admin login feature where the tests should:
Does this PR introduce a breaking change?
Other information