19 Matching Annotations
- Nov 2023
-
docs.cypress.io docs.cypress.io
-
logging in
-
-
docs.cypress.io docs.cypress.io
-
Logging In
-
-
github.com github.com
-
github.com github.com
-
github.com github.com
-
-
Capybara.string(response.body)
const $html = Cypress.$(body)
-
-
github.com github.com
-
github.com github.com
-
github.com github.com
-
// oftentimes once we have a proper e2e test around logging in // there is NO more reason to actually use our UI to log in users // doing so wastes a huge amount of time, as our entire page has to load // all associated resources have to load, we have to wait to fill the // form and for the form submission and redirection process
-
- Dec 2022
-
www.youtube.com www.youtube.com
- Jun 2021
-
evilmartians.com evilmartians.com
-
That’s not the only way of writing end-to-end tests in Rails. For example, you can use Cypress JS framework and IDE. The only reason stopping me from trying this approach is the lack of multiple sessions support, which is required for testing real-time applications (i.e., those with AnyCable 😉).
-
- May 2020
-
docs.cypress.io docs.cypress.io
-
When you’re writing tests for a very specific feature, you should use your UI to test it. But when you’re testing another area of the system that relies on a state from a previous feature: do not use your UI to set up this state.
Login flow testing in Cypress
-
- Nov 2019
-
www.valentinog.com www.valentinog.com
-
gist.github.com gist.github.com
-
github.com github.com
-
github.com github.com