How to use formatTypedArray method in Cypress

The test works when setting form: false.

it.only('PUTs a request', () => {
  const url = 'http://localhost:3000/mythings/2'
  cy.request({
      method: 'PUT',
      url: url,
      form: false,
      body: {
        name: 'Name',
        subjects: []
      }
    })
    .then((response) => {
      expect(response.body).to.have.property('subjects');
      const {
        subjects
      } = response.body;
      expect(subjects.length).to.eq(0);
    });
})

I set up a local rest server with json-server to check out the behavior.

If I try to PUT a non-empty array with form: true

cy.request({
    method: 'PUT',
    url: url,
    form: true,
    body: {
      name: 'Name',
      subjects: ['x']
    }
  })

looking at db.json after the test has run, I see the item index migrating into the key,

"mythings": [
    {
        "name": "Name",
        "subjects[0]": "x",
        "id": 2
    }
],

so perhaps form means simple properties only.

Changing to form: false gives a proper array

{
  "mythings": [
    {
      "name": "Name",
      "subjects": ['x'],
      "id": 2
    }
  ],
}

which can then be emptied out by posting an empty array.

You must write a recursive promise function, try the following

function checkCookie() {
  // cy.getCookie returns a thenebale
  return cy.getCookie('token').then(cookie => {
    const tokenDuration = getTokenDuration(cookie.value);
    // it checks the seconds right now, without unnecessary waitings
    if(tokenDuration.asSeconds() !== expectedDuration.asSeconds()) {
      // waits for a fixed milliseconds amount
      cy.wait(100);
      // returns the same function recursively, the next `.then()` will be the checkCookie function itself
      return checkCookie();
    }
    // only when the condition passes returns a resolving promise
    return Promise.resolve(tokenDuration.asSeconds());
  })
}

Then("sa session s'ouvre pour {SessionDurationType}", expectedDuration => {
  cy.get('@graphql').then(() => {
    checkCookie()
      .then(seconds => {
        expect(seconds).to.equal(expectedDuration.asSeconds())
      })
  })
})

Note that the function must be improved because

• I didn't parametrize the expectedDuration etc. (it's out of the scope of showing you how to do that)
• it waits forever without a loop counter check

But it works (I checked in another context before replying to you) and if you have some more troubles please share a "working" GitHub repo so I can clone and check it with your own solution.

Let me know if it isn't enough clear ????

UPDATE

We (me and Tommaso) have written a plugin to help you with this kind of checks, its name is cypress-wait-until.

Please thank the Open Source Saturday community for that, we developed it during one of them Saturdays ????

Try something like this:

Cypress.on('test:after:run', (test, runnable) => {
if (test.state === 'failed') {
    const screenshotFileName = `${Cypress.config('screenshotsFolder')}/${Cypress.spec.name}/${runnable.parent.title} -- ${test.title} (failed).png`
    addContext({ test }, screenshotFileName)
}

})

Below

Here comes the human tester that kills the reCaptcha manually IF NEEDED

insert

cy.intercept('POST' , 'https://www.google.com/recaptcha/*').as('googleCaptcha') 
cy.wait('@googleCaptcha').its('response.statusCode').should('eq', 200)

This looks over complicated. I would approach it by waiting for initialValue, then waiting for a different value.

cy.get('input').should('have.value', 'myInitialValue');     // wait for initial value
cy.get('input').should('not.have.value', 'myInitialValue'); // wait for it to change

.should() will retry the assertion up to 4 seconds.

If by 'several seconds' you mean more than 4, you can add a timeout option, which is better than an arbitrary wait because it will continue as soon as the assertion passes.

I'm assuming your element is an input since you are accessing val not text.

From cypress.d.ts

interface Cypress {
  /**
   * Returns specific environment variable or undefined
   * @see https://on.cypress.io/env
   * @example
   *    // cypress.json
   *    { "env": { "foo": "bar" } }
   *    Cypress.env("foo") // => bar
  */
  env(key: string): any
}

so you can extend it with

declare namespace Cypress {
  interface Cypress {
    env(key: "example"): string
  }
}

which gives intellisense (method) Cypress.Cypress.env(key: "example"): string (+6 overloads)

Create .nycrc file in your root folder and:

{
  "all": true,
  "include": [
    "pkg1/src/**"
  ],
  "exclude": [
    "**/test/**"
  ],
}

If the pattern is consistent, i.e the parent <td> contains two divs and at least one of those divs should have the search term, then work with the parent.

cy.get('[data-cy="person-name"]').should('be.visible')
  .each(($item) => {
    cy.wrap($item)
      .parent()
      .should('contain', 'SearchtermF')  // checks all children of <td>
  })
})

You may just be able to get the cells directly if there are no others on the page

cy.get('td').should('be.visible')
  .each(($td) => {
    cy.wrap($td)
      .should('contain', 'SearchtermF')  // checks all children of <td>
  })
})

This will not work because of the asynchronous nature of Cypress. Cypress themselves advises to use aliases to save values for later use.

https://docs.cypress.io/guides/core-concepts/variables-and-aliases

In you example you can put the value of cy.url() in an alias. Which you can get via cy.get('@aliasName') later:

Example:

    cy.url().as("schoolDistrictViewLink1");

    // do other things

    // when you need to use the value
    cy.get("@schoolDistrictViewLink1").then((url) => {
      cy.log(url);
    });