My cypress always stops running. Does anyone know why? - cypress

My cypress starts working fine. I am trying a simple cy.visit() test. However, it breaks all the time. Has anyone had this problem? Sometimes, it just keeps loading and loading and breaks.
image of cypress loading and breaking
I thought it could be a problem with the version. I tried installing an older version and deleting the whole folder of cypress when uninstalling it, but it has not worked.

Related

Cypress freezing (Your tests are loading)

Cypress for me is often stuck in the "Your tests are loading" screen. I am really confused as to why it happens, and restarting Firefox/crome doesn't help either. It doesn't depend on any code, happens completely randomly and today my luck was down so I was looking more at that then at my code. any help is welcome, and thank you in advance.
Late reply, but are you using webpack-preprocessor? I am and the same issue happened to me when I upgraded to Webpack 5 lately.
The solution was to downgrade to Webpack 4.
In this case it is a known issue, there is an open Pull Request on Cypress github that should hopefully fix it: https://github.com/cypress-io/cypress/pull/15611
If you're coding a project that's using another version and you install the project without using nvm use it will install the latest dependencies which may break the code that doesn't support the new dependencies version.
Check the original code Webpack version and be sure it is the same installed locally

Firefox can't load temporary addon: Error: Can't find profile directory

I'm starting to work on a small firefox plugin, it's a basic js script, no problem on this side.
I've made a few successfull tests, and had a a few satisfying results. But starting yesterday, i'm unable to laod any temporary addons in firefox.
Everytime i try to start one (even a simple console.log("hello world")), i get the error message in the console:
Error: Can't find profile directory. XULStore.jsm:66:15
It work perfectly 2 days ago, the problem appeared yesterday, and, as far as i know, i didn't made any firefox upgrade.
I've made a few reseach, a found two usefull links, one on discourse.mozilla of someone that has the exact same problem ... but no answer, and another one on bugzilla saying this bug won't be fixed because it should last long ... https://bugzilla.mozilla.org/show_bug.cgi?id=1548017
I'm askign here because i can't find any solution to my problem, and right now, it's been 24h since i'm stuck in my development progress. I'm open to any suggestion that might work.
I've checked my profiles directory and files, they're existing and ok... and that's basically everything. I'm not familiiar with the tools available for firefox so, i might have forgotten to check basic things that might help.
P.S: i'm not using selenium at any time (i've seen a few requests here about a similar issue with selenium, but i'm writing vanilla JS here, so, i think it's not the same issue)

running unit tests causes .NET Core Host to stop working

This just started happening. I've been running my tests successfully for weeks but all of a sudden I get this error (see screenshot):
When I debug, it takes me to places in my mocks where I'm setting up GUIDs. I've tried commenting those out and then it fails on other things. What's weird is that I can build and run the solution just fine in my browser, it's only my test project that is causing this issue.
I have rebooted, doesn't fix it. I have another solution that is scaffolded almost identically to this one that is running the tests just fine.
...not really sure where to look next?

RPC Server Unavailable error on TestComplete 11

I am hoping someone here can at least point me in the right direction to solving this frustrating issue. The smartbear community had no response.
I have a bunch of tests set up in TestComplete to test a web application. When I run them all at once, I consistently get an RPC Server Unavailable Error. I have no idea what this means. When I run the tests individually, there is no issue with the scripts.
I have tried running them in a script, calling them from a keyword test, and just using the project set up to call them all in order. No dice. Running each test manually completely defeats the purpose of automation.
Any ideas on how to fix this or at least where the F*** to start?? I did not have this problem with TC10, only when I upgraded to TC11
Thanks
So, in each of my modules, I was opening and closing Chrome. I decided to try taking out the close statement. Boom, no error. It still refreshes the page, which is fine. I don't know why this was a problem, but I got it to run all the modules concurrently

require-less throwing lessc error in firefox

So I'm working with RequireJS and BackboneJS. I can get everything to work fine in Chrome but when I load up in Firefox I'm getting that lessc is not defined. Obviously pulling out the less files will prevent the error from occurring. Does anyone have any ideas why require is unable to load lessc in firefox but its doing fine in chrome?
Screenshot:
http://screencast.com/t/WenocFdCA0V
Video w/ lessc not being defined in Chrome but not Firefox
http://screencast.com/t/ac96qZrpQb3R
Let me know what other info may be useful.
Thanks in advance!
Seth
less.js is broken, because it uses loadStyles before it defines it, and Firefox stopped hoisting functions according to the spec. There are probably more such mistakes, but this is the first one that is triggered during execution. Please note that the minified version is not affected because of the minification rewriting the code.
less-require is similarly broken, as it contains less.js and therefore contains the same bug.
You might want to replace lessc.js in require-less with the 1.5 beta or master version of less.js to work around this, or wait for upstream to officially release it and require-less to pick it up.
However, it appears that lessc.js is a modified version, so it isn't likely as easy as replacing the file. You would need to merge the changes back.
It might be easier just to move the affected latedefs around until it runs correctly instead of upgrading to a later less.js version.

Resources