Earlier i was using cypress-localstorage-commands package to restore caches.

Hey @proud-traffic-2752 Were you able to find any solution ?

Hey guys, I've set up an AWS code pipeline that have my cypress tests that run after every merge before deployment. The issue is that I don't want the code to deploy if any of the cypress tests fail. I can't seem to find a solution online. Most of the articles refer to stopping remaining cypress tests if one of them fails, but that will still cause the code to deploy. Has anyone come up with a solution? Thanks

Ive never used AWS CodePipeline but you likely want the deploy stage to have a dependency on the stage that runs Cypress.

Thanks!

I don't need it downloaded at all--I just want to test that the link works, actually!

is there a reason you don't want to visit or click on the link? request probably introduces quite a bit more memory overhead for large requests (requests via node, serialize data over websocket, stream to chrome)

Does anyone know of any good testing-focused podcasts? Ideally with discussion of automation, but could also just be about testing theory / QA best practices, etc.

I am getting exit code 255 before completing the action in github.. does anyone has any way to fix it..? Here i am using docker image

Hi all, how do you handle multiple waits? Though in my testRunner its passing but in CI its failing

Hi, I'm having issues with Cypress and Azure Devops Pipelines. Whenever the tests are done and all specs are succesfully passed it just hangs and never continues / finishes. If i run the exact same script in my local terminal it works just fine. Has anyone experienced or know of a fix?

Hi I am getting this error when running cypress (9.7.0) Test case with Cucumber in Jenkin. Pls help

Hi all how do you handle multiple waits

Have you run npm install?

Otherwise check that this is in your plugins/index: const cucumber = require('cypress-cucumber-preprocessor').default module.exports = (on, config) => { //

on

is used to hook into various events Cypress emits //

config

is the resolved Cypress config on('file:preprocessor', cucumber()) }

Hmm... seems to be a Jenkins issue. Maybe try this solution: https://github.com/badeball/cypress-cucumber-preprocessor/issues/437#issuecomment-722605804

In the cypress introduction there's the following

cy.get(':checkbox').should('be.disabled')

I don't understand the colons in

:checkbox

and I couldn't find anything to explain it, could anybody explain?

Is there any reason why the tests are running really slow after migrating to 10.0.0? - I just upgraded to 10.0.0 - The migration configs were done via cypress open - Then ran the tests locally via electron - At the visit, its taking a long time to load the page Any help would be much appreciated

@aloof-artist-57349 check this https://github.com/cypress-io/cypress/issues/18740 (no solution)

Thanks @handsome-lion-1748 for responding. I think I saw that issue as I was looking around for a solution but I was on 9.5.4 before upgrading to the latest version of v10

How do I record videos only for failure tests instead of every test? I want to only record video when tests or atleast one test fails.

In addition to what @adorable-smartphone-87280 said, here are a few notes: - Be sure to also install and import both lodash and del - The

after:spec

data is based on the spec level, and not for each test. We consider each time the it() function is called to be a single test. So you will generally have several tests recorded within each spec file and likely several spec files within a single run: -- All videos are available for all tests within a failed spec -- All videos are available for all tests within a spec that has a flaky test -- No videos are available for tests within a spec that has both passed and has no flaky tests because the videos have been deleted Delete when specs pass: This will only upload videos for failed specs. The video playback option will be greyed out and not clickable for any spec that does not contain at least 1 failing test: https://docs.cypress.io/api/plugins/after-spec-api#Delete-the-recorded-video-if-the-spec-passed Delete when specs pass and have no flaky tests (option @adorable-smartphone-87280 provided above): This will upload both failed specs and videos for specs with flaky tests. In this case, the video playback option will only be greyed out and not clickable if all tests have passed (and are not flaky) within a spec: https://docs.cypress.io/api/plugins/after-spec-api#Delete-the-recorded-video-if-no-tests-retried

I understand how frustrating this can be, hope someone else can help

I am trying to run a test on an older version of Firefox but I keep getting this window when I try to run. This window still appears even after I have already created a profile on Firefox. Tests work fine on the latest version of Firefox, I just need it to be on Firefox 99.0.1 specifically.

is there any way in cypress to validate element exist on DOM for 1 minute and then disappear?

Wants to write something like this, but setInterval won't work setInterval(myTimer, 1000); function myTimer() { cy.validateSignalState(true,true,false) }

I thought using cypress-recurse, but if condition satisfy before one second then that bug won't get caught

https://cypress.tips/search search my videos using "after second" Plus you might want to use cy.clock + cy.tick commands to accelerate the test and check it in milliseconds rather than wait 1 minute

Thanks for reply Before your reply i made something like this const dayjs = require("dayjs"); const addOneSecond = dayjs().add(1, 'seconds').format('H`:m:`s') recurse( ()=> cy.wrap(dayjs().format('H`:m:`s')), (currentTime) => { expect(currentTime).to.equal(addOneSecond) },{ log:true, limit:20, timeout:5000, delay: 0, post(){ cy.validateSignalState(true,true,false) } } )