Issue:
In the below screenshot, an incorrect “Event Type” such as
“window:con” (not specified in the Cypress docs) is being used. Here the
Cypress is not throwing any exception or error message while execution
Screenshot:
In this demo, I will summarize my analysis of Architectural difference between Cypress and Selenium.
Kindly provide your feedback as comments whether the “Real User Actions or Behaviors” should be part of functional, API and regression test automation or tweaking of HTML or DOM should be, too be a part.
Issue:
When the dropdown is selected using Cypress and validated with
Chai assertion, the “Time Travel” feature captures incorrect details which
contradicts with the actual selection by the tool.
Screenshots:
Issue:
- When the installed local Browser version is updated to the
latest version and when the Cypress Test scripts are ran, the test scripts are
failing and the message “No Commands were issued in the test” was displayed.
- After clicking the update in the Cypress Test
runner too, the test scripts were failing.
- If I Close the Cypress Test Runner and after re-opening it,
the tests are passing.
- After local browser is updated, every new
opening of Cypress Test Runner is causing error and tests are failing.
Screenshots:
After Re-Opening the Cypress Test Runner, the test scripts
are passing:
