-
Notifications
You must be signed in to change notification settings - Fork 13
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
Set up Cypress Test for Search page #3
Comments
Writing structural tests for our landing page would be a great way to start in my opinion. |
Hey @ShubhamPalriwala Happy to see you are interested in this. The top priority to test is the search bar. |
So, I recently wrote a test suite on the merriam-websiter website wherein I tested their searchBox which can be found here. Let me know if we can proceed with this for now. |
@gsambrotta Should I proceed with it with something similar to what I've mentioned above? Awaiting your feedback |
@ShubhamPalriwala that test looks very similar to what can fit for us. I would be happy if you can share early PR, like a draft of your work in progress so we are sure you don't work for long time on something that might not be the best solution for Elliot for Water. |
Hey @gsambrotta, Can you mail me these 3 environment variables so that I start the development server as without them I cannot view the search results:
|
@ShubhamPalriwala sorry for some reason I don't get notifications from issues. I will try to keep acloser eye on this issue. |
We would like to start using End to End tests to ensure our application doesn't have unseen bugs.
We thought about Cypress since some of us have a good experience with it.
Before starting it, we would like to do a trial, create a MVP for the testing suits, to see how well it integrate with our system.
The idea would be to set up Cypress and have one or two test running.
And see what challenge we could face with it.
A good first test could be on the search page.
The text was updated successfully, but these errors were encountered: