Unexpected wrong address in the address bar
See original GitHub issueCurrent behavior:
Visiting url add in Chrome address bar which breaks test
Desired behavior:
Visiting url opens in Cypress test address bar
Steps to reproduce:
My test-case
describe('Wtf', function() {
it('Visit', function() {
Cypress.config({
baseUrl: "https://ya.ru"
});
cy.visit('/');
});
});
Versions
Cypress 3.0.2
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Address bar has mysteriously gained a black background ...
While I was using chrome, the address bar mysteriously started to have a black background. Some things say that this is a consequence...
Read more >Uncaught SyntaxError: Unexpected identifier with javascript in ...
When I want to type the following code to the address bar, the console yields Uncaught SyntaxError: Unexpected identifier .
Read more >HOW TO RESOLVE WEB SITE ISSUES Clear your Browser ...
In the search bar at the top of the screen, enter “Site Settings”. 4. Click Site Settings. ... In the address bar, enter...
Read more >How to troubleshoot the Outlook Offline Address Book in a ...
You receive the following error message when you run the Send/Receive command in Outlook in Cached Exchange mode: Task 'Microsoft Exchange Server' reported ......
Read more >Fixing Common Error Messages and Display Issues in Lexis
Note: You can also access Clear browsing data by pressing Ctrl + Shift + Del or entering chrome://settings/clearBrowserData into the address bar and ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If you are behind a corporate proxy, we recommend trying some of our workarounds detailed here: https://github.com/cypress-io/cypress/issues/1469
The original issue was never completely verified, but as some commenters had success after editing their proxy settings, I will assume this will be fixed with our upcoming 3.3.0 release of improved proxy support. https://github.com/cypress-io/cypress/pull/3531
Please comment or open a new issue if this is not the case.