How to use resolveServerConfig method in Cypress

A year later, but maybe this will be useful for somebody with a similar issue.

According to this very helpful article - https://www.cypress.io/blog/2020/07/22/do-not-get-too-detached, to implement the desired wait, you should allow application to finish action that came first, before proceeding.

My guess is that in your case, .menuElement is still not mounted in the DOM. And instead of using wait(), you could do something like this:

cy.get('.menuElement').should('not.exist');
cy.get('.menuElement').click();

You can use jquery via Cypress.$ to check if any exist.

const listItemTitle = '[data-cy-component=list-item-title]';
if (Cypress.$(listItemTitle).length > 0) {
  cy.get(listItemTitle).each(($el, index, $list) => {
    cy.wrap($el).then(($span) => {
    const spanText = $span.text();
    cy.log(`index: ` + index + ' ' + spanText);
    });
  });
}

I have updated our recipe for static resource loading, see https://github.com/cypress-io/cypress-example-recipes/pull/363

To check if an image has finished loading, the simplest way is to check the image's naturalWidth or naturalHeight property.

// we can wait for the <img> element to appear
// but the image has not been loaded yet.
cy.get('[alt="delayed image"]')
.should('be.visible')
.and(($img) => {
  // "naturalWidth" and "naturalHeight" are set when the image loads
  expect($img[0].naturalWidth).to.be.greaterThan(0)
})

Alternatively, you can use performance entries to confirm that any static resource has finished loading, see the above pull request for the details.

At the section of the code that sets the text to Finished, have it call the resolve function of a Promise constructor which is assigned to in the loop. Then, in the loop, construct the Promise and await it. For example:

let resolveFn = () => undefined;

// ...
// Run loop:
(async () => {
  // ...
  for ( // ...
  // ...
    if (state !== 'Finished') {
      const prom = new Promise(resolve => resolveFn = resolve);
      document.querySelector(...).click();
      await prom;
    }
}
})();

// ...

function clickHandler() {
  // ...
  // At the point where you assign "Finished", call the resolveFn:
  span.textContent = 'Finished';
  resolveFn();
}

If you don't have control over the code that assigns the Finished text, the other possibility to watch for the change of the text would be to use a MutationObserver, eg:

if (state !== 'Finished') {
  document.querySelector(...);.click();
  await new Promise((resolve) => {
    new MutationObserver((_, observer) => {
      if (span.textContent === 'Finished') {
        observer.disconnect();
        resolve();
      }
    })
      .observe(span, { childList: true });
  });
}

I think you're looking for --spec path/to/folder/*.js

You can run all the tests in a folder, or even in all subfolders of a folder,

ex/ npx cypress run --spec cypress/integration/subsetA/**/*-spec.js

would run all .js specs in all folders under the "subsetA" folder in cypress/integration.

So in your case: npx cypress run --spec cypress/integration/apps/smhw-qa/**/*-spec.js should do the trick.

https://docs.cypress.io/guides/guides/command-line.html#How-to-run-commands

From the documentation:

dayjs().subtract(15, 'day');

Available units are mentioned here, day is one of them.

I would assume you are just missing retries for fetching the iframe until the body is loaded. Simple get and should combo doesn't wait for this to happen. Official docs state you should use .its('body') when working with iframes, so try something like this:

cy.get('.aut-iframe').its('body').then((body) => { cy.wrap(body).should('...') }

Reference: https://www.cypress.io/blog/2020/02/12/working-with-iframes-in-cypress/#header

I implemented testing for a multi-lingual site that supported 40 language locales by using this trick:

1. Define one dictionary (JSON file) for each locale. In the locale file, define the mapping between element ID and text.

2. Write the test suite to take 'locale' as the parameter / environment variable. Test cases will refer to the appropriate dictionary file, based on the locale parameter. Test case will do the assertions based on the mappings defined in locale dictionary.

3. Run test suite with locale as the parameter. This had helped me avoid lot of if-else conditions and switch blocks!

It also helped run tests for only specific languages for a release. (Scenario where not all language sites were updated for every release)

https://testing-library.com/docs/dom-testing-library/api-queries

• getBy will throw errors if it can't find the element
• findBy will return and reject a Promise if it doesn't find an element
• queryBy will return null if no element is found:

This is useful for asserting an element that is not present.

looks like queryBy is your best choice for this problem