-
Notifications
You must be signed in to change notification settings - Fork 87
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
Add e2e tests #58
Comments
I want to work on this issue for GSOC 2023. Kindly assign to me. |
The application period opens in 4 weeks, we don't even know yet if this is going to happen or not. It's always good to get a head start though, but may I suggest a smaller issue (this is fairly big and should be tackled during GSoC), e.g. #50. That has a huge impact on UX but is not much work. |
Good Afternoon Sir,
4)In the Test Runner, click on the "example_spec.js" file to run the tests.
This test visits the homepage of "example.com" and searches for the term "Cypress" using the search input field and submit button. Then it asserts that the resulting page URL contains the search term and that the page contains a heading with the term "Cypress".
We can use the Cypress API to write more complex e2e tests for your application. Sir is my approach correct, please reply back |
Sorry, this was accidentally labeled as "good first issue". But you should have read previous comments, which clearly say |
@nilsnolde as you said its a fairly big issue , may i start with implementing basic tests like visiting the website? As im complete novice in cypress , i'll try to learn bout it and do contribution while learning? |
that'd be very nice @Ghat0tkach thanks! |
@nilsnolde , when i was installing using npm , i found a lot of libraries which have been depreciated |
Right now, we're not testing. We could add some basic e2e tests with e.g. cypress.
The text was updated successfully, but these errors were encountered: