Docs: https://docs.cypress.io | Issues: https://github.com/cypress-io/cypress/issues
cy.exec() but this results in a code of 0. Does anyone know why or how I can change it so that a non-zero code is returned?
Anyone can explain me, this error : CypressError: Timed out retrying: this.ol_originalAddEventListener is not a function
$ docker run -it -v $PWD:/e2e -w /e2e --entrypoint cypress cypress/included:3.8.0 --version
Unable to find image 'cypress/included:3.8.0' locally
docker: Error response from daemon: manifest for cypress/included:3.8.0 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
--headless --browser chrome but running cypress tests on circleCi throws errors when setting these flags. Can't run because you've entered an invalid browser name.
Browser: 'chrome' was not found on your system.
Available browsers found are: electron
Can't run because you've entered an invalid browser name.
Browser: 'chrome' was not found on your system.
Available browsers found are: electron
Xvfb exited with a non zero exit code.
There was a problem spawning Xvfb.
This is likely a problem with your system, permissions, or installation of Xvfb.
document.getElementsByTagName('video').item(0).muted = true when not using cypress
Afternoon all,|
Quick question i have a should assertion that in this particular case is comparing a null value from an array to an empty string, which is causing my test to fail.
.should("have.value", result[4]); //result[4] === null
How could cypress handle this scenario?
Hi all. I am trying to capture the exit event of cypress test in plugins/index.js
However none of the following work:
process.on("exit", flushLogs);
process.on("SIGINT", flushLogs);
process.on("SIGUSR1", flushLogs);
process.on("SIGUSR2", flushLogs);
process.on("uncaughtException", flushLogs);I don't get it. The plugins/index.js is lauched in nodejs env, so it should receive the process event.
Does anyone have an insight ?
cy.route() can't be used to mock cy.request() but nothing is said about cy.visit()
Hi all. I am trying to capture the exit event of cypress test in plugins/index.js
However none of the following work:process.on("exit", flushLogs); process.on("SIGINT", flushLogs); process.on("SIGUSR1", flushLogs); process.on("SIGUSR2", flushLogs); process.on("uncaughtException", flushLogs);I don't get it. The plugins/index.js is lauched in nodejs env, so it should receive the process event.
Does anyone have an insight ?
Hi @dwelle ! Do have any insight on this ?
Hi everyone,
Sorry if this is not the right place for such a long set of questions. But for the past couple weeks, I've been evaluating cypress as a potential tool my team could use. But it is harder for me as I am fairly new to both javascript in general and cypress. So my question is if I might get some insight from those more experienced if Cypress might be a good tool given our circumstances.
The situation is that we use salesforce as the base platform from which to build our websites. But only the very basic infrastructure and building blocks that SF offers. Once you get to our community sites, the page is built very custom with javascript that we control nearly entirely. So I definitely do not want to test anything SF specific, especially not their UI, but the fact that we are using SF at all still presents problems. Unfortunately, when I search salesforce in this chat, and on google in relation to cypress, I don't really find any solutions specific to SF, but instead a good number of problems.
The main two problems I seem to be dealing with are authentication and the fact that SF does not seem to play nice with iframes in general. I want to log in through API, but haven't figured out how that can be done successfully. So I'm pretty discouraged and thought I'd see if I could find out if using cypress in these circumstances would likely involve constant challenges to overcome, or if maybe I can get past authentication and mitigate the iframe issues, then it might be mostly smooth sailing from there. I really like a lot of the features of cypress, the testing philosophies and practices it harbors and the direction it seems to be headed in, so I wanted to at least ask directly before giving up. Even if the answer is something along the lines of 'in theory it should be possible, but we don't know if anyone has actually done much like this.' I can probably work with that. I want to know if its more like 'No, its not going to work or be very difficult because of x and y.' before I put a lot more time into it. Maybe one glimmer of hope is that I've already been able to create tests for our public facing sites that seem to run without many issues in regards to iframes, so that is one reason I hope that maybe it just authentication that I would need to overcome. Thanks a lot for any help!
One other specific question is if the advice in this thread would work to resolve the iframe issues that SF presents, or if that is a different class of issues:
cypress-io/cypress#1763
As one example, I tried to run cypress with a SF development scratch org (primarily as a route to overcome authentication), and I got this error:
SecurityError: Blocked a frame with origin "https://business-page-1769-dev-ed--c.documentforce.com" from accessing a cross-origin frame.
Does this error look like the type that can be resolved by the extension and configuration outlined in issue 1763? I'll probably give it a try next week anyway.
I could also give more details on what attempts I've made to login, if that might help in answering my concern. I've tried using cy.request to make a post to authenticate, the exact same way that we do so through postman, for example. And the request seems to work. It gets the same body back just as postman does, but it doesn't seem to translate into a cookie for cypress. The response contains these 6 attributes. I'm afraid this might represent an "API access only" type of login, which may be the underlying problem..?
"access_token":
"instance_url":
"id":
"token_type":
"issued_at":
"signature":
Last side question: Could there be a straightforward way to use the JSForce library alongside cypress for API purposes?
Here's the current appearance in the cypress ui:
