I have just created a spec file under that path is integration>mweb>account>address-mweb.spec.ts. Cypress UI sees my all spec files but while running it cannot establish a connection with tests.
How can I fix this, any idea?
p.s there is no network issue.
Waiting to connect on terminal
Cypress UI appearance
Is it the same with Electron, seems the issue with the chrome browser. Before checking others, please try with Electron
Update the cypress version to the latest. It might help you to fix the issue.
maybe check your hosts file, see whether
127.0.0.1 localhost
is in there
Related
I am writing a fixture, and multiple tests assert the page's title to be some value. However, I did not account for the fact that the website is localized. My normal browser settings are English, but when I run the testcafe chrome:headless myTests.js my tests fails because the Localization changes, perhaps due to my PC's language?
I have tried running my local chrome installation and adding :userProfile, but without luck sadly.
The only other information I can find regarding this issue is, but I can't make it work:
TestCafe & chrome:headless : how to force the browser language (locale)
I found my answer here - go give them a like if it solves your issue as well.
Solution:
I use the following command to launch chrome headless with a locale specified:
testcafe chrome:headless --lang=en-US
I am attempting to run a test on our Electron app using TestCafe. I have tried many things but after many hours am still getting the error below:
"ERROR Unable to establish one or more of the specified browser
connections. This can be caused by network issues or remote device
failure."
The cases I have read Googling around do not seem to apply to my case.
I have everything set up as described here: https://github.com/DevExpress/testcafe-browser-provider-electron#testing-an-executable-electron-application
The .testcafe-electron-rc file is correct in that my app does indeed launch but errors as above. I do not think it gets to my script which is very simple for debugging purposes. I have tried changing the mainWindowUrlPath to various locations since it seems like my app is run from C:/Program Files/MyApp/resources/" which contains an app.asar file even though our app is located in "C:/Program Files/MyApp/MyApp.exe"
I have tried setting up the .testcafe-electron-rc in many configurations including the one described in the documentation as well as many others. An example is below which I realize is non-standard:
{
"mainWindowUrl": "C:/Program Files/MyApp/resources/app.asar/index.html",
"electronPath": "C:/Program Files/MyApp/MyApp.exe"
}
Note, I have never seen the index.html anywhere in the app directory but assume that TestCafe must dive into the asar in some manner.
I have disabled the Windows firewall but still, the same issue exists.
I have run my tests with nodejs installed globally and testcafe and the Electron provider installed globally and locally (i.e. run these configurations separately) but the same issue occurs.
Does anyone have any other ideas? Any help appreciated.
This is on Windows 10.
m
My project is built using Vue.js, powered by Nuxt
I’m using Cypress to write/run tests
I’m using CircleCI (v2) to run the tests
Locally, using Cypress’s instance of the Electron browser on macOS, the tests run correctly.
On CircleCI, the tests display a blank screen.
I’ve SSHed into CircleCI after the tests have failed, and if I make a curl request to the local server at that address, the correct HTML is returned to me.
My hypothesis is that the browser is not able to run Vue.js, but without a console log it’s hard to tell.
Any ideas as either how to continue debugging, or even better, fix it?
Edit: I’ve written an extra test to use another site, and it loaded correctly, so I can confirm that everything else is working.
Edit: It’s in my Nuxt config, just going through it now to pull out the line causing the problem.
So, of course this was super annoying. I’m not sure what the chances are of this happening to somebody else, but here’s the answer to my problem:
Google Analytics
On my CI I don’t have a GA code, and it was falling back to empty string, so it wasn’t able to load the page. It didn’t show up on the sever logs as it was an issue on the client side, and it’s not yet possible to easily get client logs using Cypress (coming soon).
Interesting, Thomas,
Could you open a GitHub issue with a link to a small repo that we can try ourselves? I do not see any factors that might affect running Cypress tests against Nuxt app on Circle
I am using version 4.5.5 of jhipster.
My OS is Linux Mint.
I am using IntelliJ as my IDE.
Everything is working fine in terms of generating the code, building and running the code.
Client
Unfortunately, when I make changes to the client code (html or ts), the changes are not reflected until I recompile the client code completed. To achieve this I do "mvn -Pdev,webpack". It takes quite a while to restart the client and this is really holding me back.
Hot Deploy
What I expect to happen is that I can run "npm start" and when I save a change to a ts or a html file that it will be picked up and the change immediately visible in the browser.
Questions
Any ideas why the client hot deploy is not working ?
Any ideas how I identify where the issue is ?
For example, how do I know what folders are being watched by the hot deploy ?
Thanks a million for you help.
I am sure others have encountered the same issue and will read the answer gladly.
Kind regards,
Fergal.
PS Need any details, simply ask.
Figured it out.
Somebody else had a similar issue with a globally installed instance of webpack.
I installed a local version and the file updates are being detected and recompiled and the app hot deployed. Now working perfectly.
To install a local version webpack.js.org/guides/installation/#local-installation.
Trying to run Capybara tests with Selenium is failing for me because the "Welcome" page (https://www.mozilla.org/en-US/firefox/45.0.1/firstrun/learnmore/) pops up no matter what preferences I set. I assume this is because Selenium is using the default profile, and while I've found some information on configuring user.js and prefs.js in the mozilla profile folder, nothing I've tried has worked.
Has anyone else figured out how to configure Firefox to prevent the welcome page from killing your tests? If so, please share!
Just found a work-around, I was able to introduce a 1 second pause as the first command, give that a shot.
I settled on a workaround for this issue. Unfortunately, it is to use the Chrome driver and abandon Firefox altogether. Sorry Mozilla.