navigateTo() returns error
See original GitHub issueAre you requesting a feature or reporting a bug?
bug
What is the current behavior?
.navigateTo()
always returns an Uncaught SyntaxError: Unexpected identifier
What is the expected behavior?
.navigateTo()
should navigate to the specified web page.
How would you reproduce the current behavior (if this is a bug)?
Pretty straightforward, any test (a relative or absolute URL path) and then wait()
.
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
await t
.navigateTo('https://google.ca/')
.wait(1000)
Specify your
- operating system: Windows 10
- testcafe version: 0.11.1
- node.js version: 6.9.1
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
asp.net core - NavigationError on NavigateTo - Stack Overflow
I'm trying out Blazor ServerSide and created a Component to Redirect To the Login Page when a user is not logged in. @inject...
Read more >getting an error when trying to use NavigationManager ...
I am trying to navigate to another page using NavigationManager.NavigateTo and I keep getting this error saying:
Read more >Navigate with named routes - Flutter documentation
Create two screens. Define the routes. Navigate to the second screen using Navigator.pushNamed() . Return to the first screen using Navigator.pop() .
Read more >Page Object .navigate() returning a type error - Google Groups
navigate() but an error is returned on that line that says 'undefined is not a function'. Is this a bug with Page Objects...
Read more >Flutter: Navigate to a new screen error in MaterialApp
It is because there are some issues with MaterialApp context. The Navigator won't work if you're doing in under MaterialApp context. void main()...
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
It seems that
testcafe -e ...
arg does the trick. I think this ticket can be closed!Actual documentation for the open-source TestCafe version is here: https://devexpress.github.io/testcafe/documentation/getting-started/
You can find how to ignore js-errors on the page in the Command Line Interface article