🐛 Bug report: Cypress is not throwing exception or error message when wrong “Event Types” are used

 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:

Analysis of Architectural difference between Cypress and Selenium

 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.

🐛 Bug report: Cypress “Time Travel” feature fails with Chai Assertions

 

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:

🐛 Bug report: Cypress Tests are failing after the updating the Browser to Latest Version

 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: 

[🐛 Bug]: WebDriverManager with the "MatchingBrowser" command displays error in Selenium C#

When the WebDriverManager is instantiated with the "MatchingBrowser" command, the browser is not launched and error is displayed

Screenshot:

[🐛 Bug]: Selenium4, CSharp & WebDriverManager is not downloading the latest version of EdgeDriver and throwing error

 

When the Edge browser is upgraded from “102.0.1245.44” to “103.0.1264.49 ”, the latest EdgeDriver such as “103.0.1264.49 ” is not downloaded by the WebDriverManager and test scripts are failing.

Screenshots:

Error Details:

EdgeDriver latest version not downloaded details:

Installed Edge Browser version:

[🐛 Bug]: Selenium4, Java & WebDriverManager downloads improper versions of drivers and test executions are failing

 

When old versions of Chrome/Edge/Firefox are installed and when the WebDriverManager is used/run, it downloads the incorrect version of chromedrive.exe or respective drivers and hence the test executions are failing.

Screenshots:

Error Details:

Browser Installed Version:

[🐛 Bug]: Selenium4, CSharp & WebDriverManager downloads inappropriate versions of drivers and test executions are failing

 

When old versions of Chrome/Edge/Firefox are installed and when the WebDriverManager is used/run, it downloads the latest version of chromedrive.exe or respective drivers and hence the test executions are failing.

Screenshots:

Error Details:

Browser Installed Version:

WebDriverManager driver downloaded details:

[🐛 Bug] Selenium4, C#, Java & WebDriverManager, latest version are not working and throwing errors

 [🐛 Bug]:  Selenium4 & WebDriverManager latest versions are not working and throwing errors

Scenario 1: 

The WebDriverManager/Driver throws error when the URL is passed without "http://" or "https://"

Screenshot:

Error Details:

Scenario 2:

The WebDriverManager supports only the stable version and not Beta version

Browser .exe downloaded and available details:

Version Details:

Please Note: In some test scenarios the beta version is also used for testing