mysterious-belgium-25713
12/06/2022, 8:06 PMmelodic-account-9605
12/06/2022, 8:57 PMcy.intercept()
in a beforeEach()
to intercept graphql requests, and finding that it's still intercepting requests that I'm making from my after()
. That's not expected behavior right?dry-ice-92667
12/06/2022, 9:10 PMmysterious-belgium-25713
12/06/2022, 9:48 PMmelodic-account-9605
12/06/2022, 9:57 PMfew-laptop-73260
12/06/2022, 11:16 PM"react-scripts -r @cypress/instrument-cra start"
to generate the .nyc_ouput
file needed to generate coverage.
When running cypress on the pipeline, I give him an external URL where my react app is deployed (GitHub pages). However, I am not able to generate the instrumentation for it on the pipeline. Do you know any ways I could generate this .nyc_output
without having to add it to a script and run my application? Is there any way to generate this .nyc_output
just with a command analyzing the code?
> I am guessing a command like this exists because of a peculiar behavior I noticed. When running my application with npx cypress run --headless
it does not generate the nyc_output
. However, when I run opening the interface with npx cypress open
and clicking to run the tests, it can generate. But I have no idea what is the difference between the headless option and the interface one.
Thank you in advance.fierce-activity-35946
12/07/2022, 12:41 AM12.0.0
, when the cy.session()
is being restored
in the middle of the test, the next immediate cy.visit()
action in the same test (it() block) is not working, it is not navigating to the page due to which the test fails. It is not navigating to the page due to 401 issue which is not expected here as we are using an already restored and authorized session.
Is this behavior expected or this is a bug?helpful-hairdresser-46183
12/07/2022, 6:13 AMenough-fireman-4779
12/07/2022, 10:38 AMhelpful-hairdresser-46183
12/07/2022, 11:53 AMvictorious-summer-2999
12/07/2022, 1:11 PMthankful-lock-39376
12/07/2022, 1:13 PMvictorious-honey-34966
12/07/2022, 1:36 PMgray-kilobyte-89541
12/07/2022, 2:09 PMlemon-wall-91819
12/07/2022, 2:25 PMlemon-wall-91819
12/07/2022, 2:26 PMgray-kilobyte-89541
12/07/2022, 2:31 PMflaky-horse-36126
12/07/2022, 2:44 PMlemon-wall-91819
12/07/2022, 2:45 PMdry-scooter-25612
12/07/2022, 4:07 PMvictorious-summer-2999
12/07/2022, 4:34 PMenv: {
...
grepTags: '-flaky+-bug+-notReady+-notReadyForStaging+-notReadyForDesktop',
grepFilterSpecs: true,
},
then the spec file:
it(
'Verify that feature impression event is triggered when the MOV hint is in the viewport',
{tags: [Feature.gtm, Feature.mov, Status.notReady]},
function () {
...
},
);
CLI command:
yarn e2e --command open --env production --platform desktop --locale de_DE --browser chrome --grepTags="-flaky+-bug+-notReady+-notReadyForStaging+-notReadyForDesktop"
the spec above contains tags notReady
and it gets executed anyway
@gray-kilobyte-89541
I tried also to replicate a simple test like this:
it('works as an array', { tags: ['@slow', '@smoke'] }, () => {
expect(true).to.be.true
})
it('works as a string', { tags: '@regression' }, () => {
expect(true).to.be.true
})
with command npx cypress open --e2e --env grepTags='@slow @regression --@smoke'
and it executes all tests...bitter-fountain-36713
12/07/2022, 4:35 PMnutritious-analyst-96582
12/07/2022, 4:35 PMstrong-fountain-85853
12/07/2022, 5:33 PMmysterious-belgium-25713
12/07/2022, 5:53 PMechoing-actor-29720
12/07/2022, 8:25 PMechoing-actor-29720
12/07/2022, 8:29 PMloud-park-10778
12/07/2022, 8:52 PMloud-park-10778
12/07/2022, 8:53 PMbitter-fountain-36713
12/07/2022, 9:56 PM