How to use firefoxUtil.setupMarionette method in Cypress

There is the oneOf assertion if an exact match is is acceptable.

cy.get('element')
  .should('satisfy', ($el) => {
    expect($el.text()).to.be.oneOf([value1,value2])
  })
  .click()

Looks like only one param is handled. But you can always pass in an object with the vars as properties.

 on("task", {
    async "rename"({var1, var2, var2}) {

 }

and in the .spec call it as

cy.task('rename', {var1: 'val1', var2:'val2', var3: 'val3'}, ()=>{
            console.log('renamed');
       })

What you need to do is first start waiting for the response and then click, so the waitForResponse() can catch the actual response coming as a result of the click.

await Promise.all([
    page.waitForResponse(resp => resp.url().includes('/api/contacts') && resp.status() === 400),
    contacts.clickSaveBtn()
]);

This should handle the possible race condition.

I guess you need to enter npx cypress open if you are running for first time. once the project is created then you can use npx cypress run

Set type to {selectall} - https://docs.cypress.io/api/commands/type.html#Week-Inputs

cy.get('.editor').type('{selectall}');

You can do this by overwriting cy.visit() command. Try this:

Cypress.Commands.overwrite('visit', (originalFn, url, options) => {
  originalFn(url, options);
  // make sure to add a return here!
  return cy.get('body').then($body => {
    if ($body.find("[text='Got it']").length > 0) {
      cy.contains('Got it', { matchCase: false }).click();
    }
  });
});

source: https://docs.cypress.io/api/cypress-api/custom-commands#Overwrite-visit-command

After a while I did a deeper search in the cypress issues.

I found a comment talking about a problem in some situations when NOT using localhost as server name (I was using custom TLD with Valet for Linux, so it was very related to my problem). I hope that if you are in my situation you don't need to dive in along the same process.

So I check with the new configuration and MAGICALLY all works!.

All i did is Boot up a server using localhost and then run the tests(automatically or with cypress UI)

// package.json
// 'npm test' to run tests automatically
// 'npm run test:ui' to run with cypress UI 
"scripts": {
    "start": "http-server -a localhost -p 3030 -c-1",
    "cy:run": "cypress run",
    "cy:ui": "cypress open",
    "test": "start-server-and-test start http://localhost:3030 cy:run",
    "test:ui": "start-server-and-test start http://localhost:3030 cy:ui",
  },`

I have shared the first attempts in a repository.

Dune Browsing - Exploring testability of service workers in offline mode.

I've tried setting them in a before() but that didn't work either.

The before block should work. Maybe the before block isn't setup properly? I'm able to get this to work using the following setup.

describe("Foo Fighter", function() {
    var foo;
    before(function () {
        foo = getRandomArbitrary(1,10,1);
    });

    it("Fighting foo 1", function () {
        cy.log(foo);
    });
    it("Fighting foo 2", function () {
        cy.log(foo);
    });
    it("Fighting foo 3", function () {
        cy.log(foo);
    });
});
function getRandomArbitrary(min, max, decimals) {
  return (Math.random() * (max - min) + min).toFixed(decimals);
}

Which produces the following result, the random number staying the same during each it block.

The logic flow goes:

• In the describe block, declare your variable.
• In the before block, set your variable using the random number.
• In the it block, use the set variable.

EDIT:

To answer your comment:

If I set it like you it works fine, but imagine if in the first it you visit google, and in the second it you visit github, the before block will run twice

The issue here is that when you visit a new site, Cypress reloads the entire test context, so a before block, like you mentioned, will be run again each time the test context is reloaded (i.e. each time a new domain is visited).

The way around this is to cheat by setting up another describe that runs first and writing your variables to fixtures and using those fixtures in your test, like so:

describe("Before Describe", function(){
    const foo = getRandomArbitrary(1,10,1);
    it("Setting up test context", function() {
        cy.writeFile("cypress/fixtures/test.json", { "foo" : foo});
    });
});



describe("Foo Fighter", function() {
    it("Fighting foo 1", function () {
        cy.visit("https://example.cypress.io");
        cy.fixture("test.json").then(kung => {
            cy.log(kung.foo);
        })
    });
    it("Fighting foo 2", function () {
        cy.visit("https://google.com")
        cy.fixture("test.json").then(kung => {
            cy.log(kung.foo);
        })
    });
    it("Fighting foo 3", function () {
        cy.fixture("test.json").then(kung => {
            cy.log(kung.foo);
        })
    });
});

function getRandomArbitrary(min, max, decimals) {
  return (Math.random() * (max - min) + min).toFixed(decimals);
}

This will produce the following results:

Admittedly, not the cleanest way to construct your testing flow, however, it produces the result you're after. Should also work if you put the setup in an it that comes first within the same describe as the other tests.

Can you explain more detailed what you wanted with that ip ?

In many cases baseURL is localhost or 127.0.0.1 - this will work anytime because is "your computer" (loopback).

You can use ip that is assign to your network, but be careful because it can change.

Also I wanted to force cypress to "see" me as different ip, from different region, but this is possible only if using VPN (on linux you have windscribe; in windows you have Hotspot Shield)