Might help a reproducing git hub repo - Even if you want to create a issue, reproducing example would help to anyone who wants to investigate and help

Thanks

onclick system redirect user to another domain & system remove Spec window ( how we can resolve this ) & showing redirect URL in window without Specs window @stocky-dream-36427 @wonderful-match-15836 @best-flower-17510

after this window system remove Spec window & stop everything

Hello again, I am pretty new to Cypress and my organization is planning on reverting back to 9.7.0 to continue to make use of the Cypress Studio. We have been using the badeball Cypress-cucumber-preprocessor and bahmutov's esbuild preprocessor, is there a guide out there for using Cypress 9.7.0 with these tools?

I have a custom command for logging in via API, and I'm calling it in the before hook, but the session isn't being preserved between tests. All the examples in the docs show the login being called in beforeEach. If I'm logging in before each test, is the session even being preserved across tests or am I just logging in before every test?

session is not preserved across tests

Yeah we ran in to this when we first started with Cypress at our company. Our work around was to copy the cypress (it’s specific) local state between tests

Do you by chance have an example of how that's done?

Yea, let me see if I can pull it up

Hi, I'm having issues with the installation of Cypress, I can't locate the cypress.config.js file

Not entirely sure if this is hacky or not, but it's worked flawlessly for us for a while now.

let LOCAL_STORAGE_MEMORY = {};

Cypress.Commands.add("saveLocalStorage", () => {
    cy.window().then(window => {
        Object.keys(window.localStorage).forEach(key => {
            LOCAL_STORAGE_MEMORY[key] = window.localStorage[key];
        });
    });
});

Cypress.Commands.add("restoreLocalStorage", () => {
    cy.window().then(window => {
        Object.keys(LOCAL_STORAGE_MEMORY).forEach(key => {
            window.localStorage.setItem(key, LOCAL_STORAGE_MEMORY[key]);
        });
    });
});

put that into your commands.js, and then at then at the top of your tests after your

describe(

and before your first

it(

test, call it this way:

beforeEach(() => {
        cy.restoreLocalStorage();
    });

    afterEach(() => {
        cy.saveLocalStorage();
    });

awesome, thanks I'll give that a shot!

Hey all, does anyone from Cypress have any ideas about this? https://discord.com/channels/755913899261296641/755913900024791046/1010101418067238952

I must be missing something. I am trying to write a password reset test. Our validation uses Firebase, and so the password reset link gets sent to the user email, I can get the link utilizing Mailosaur. However storing that link as a variable (as per Mailosuar's own documentation) and attempting to

cy.visit

it results in it getting tagged with the

baseUrl

. From what I've read, you're not supposed to navigate to external sites within the same test. It looks like there's the option to enable the experimental feature (

cy.origin

) but that seems like a lot. The other option I'm seeing is

cy.routing

but I'm not sure that's what I'm after. Does anyone here have practical experience with Mailosaur and navigating through an email link in one test?

I had to set up a custom function to get around the cross-visit issue. Goes against their rules, but we needed to do it on our application.

Cypress.Commands.add('crossVisit', (crossUrl) => {
    // this is a workaround due to the fact that Cypress currently does not support hitting a different super domain with .visit()
    cy.window().then((window) => {
        window.location.assign(crossUrl);
    });
});

Hi All, Is there any way to validate the attachment in the email using cypress? please

You might need to give this a read https://github.com/mailosaur/cypress-mailosaur

How do I get the results of multiple `Chainable`s?

Also, if my markup looks like

<h1/><div><h2/></div>

, what's the most efficient way to get from the h1 to the h2? I'm thinking of some function like

.next("h2")

that does preorder DOM traversal.

Hi all, How would you solve the following type error, also how would you type to be fine with Typescript and Cypress?

API.getAccessCodes(id).then((response: **GetCodesResponse**) => { // error 1
          expect(response.success).to.be.true; // intellisense work here as expected
          expect(response.data.code).to.equal('12345678'); // intellisense work here 
        });

// error 1: 
// No overload matches this call. Argument of type '(response: GetCodesResponse) => void' is not assignable to parameter of type '(this: ObjectLike, currentSubject: Response<any>) => void'.

// API.getAccessCodes(id: string): Cypress.Chainable<Cypress.Response<any>>

getAccessCodes

return the

cy.request()

, and the above example works as expected, however I cannot seem to resolve the issue with the response type, and if I do, TS loses the ability to have intellisense inside the

.then()

Custom External Site

Hi Team, hope somebody knows how can I solve the integration of clickhouse into the project? Like I need to make queries from test to clickhouse base and get a response by these queries and work with this response. Because cypress runner doesn't handle this yet, I all-time get an error like > URL is not a constructor?

Hi Team! I would like to know if anyone has implemented a parametric login that I can run in different environments using the credentials according to the test environment (qa, dev, prod). the version of cypress that I am using is 10?

Yeah, I've achieved this in the past by having the credentials passed in as environment variables

excellent Liam, you know how to do it in version 10 of cypress. Might you help me? I am very new to this framework. Any documentation or tutorial that can help me, I appreciate it.

As for documentation, I think this is the one that might be helpful in order to achieve what Liam suggested https://docs.cypress.io/guides/guides/environment-variables

thanks marian! I was also reviewing this content and implemented it in the tests. But when running the login test I have problems with the variables that are entered to write in the texbox field https://talkingabouttesting.com/2021/10/09/como-fazer-login-com-cypress-em-diferentes-ambientes/

@early-optician-55799 look mariana, when implementing the content of the blog and running the test it throws me this error

As much as I would love to help, I'm a newbie when it comes to Cypress or even coding in general :). I've just came to look for help as well and it just happened that I have been searching through environment variables topics as well so I passed the link to the documentation I've just read myself 😉