Selector is influenced by assertions

Current behavior:

The same selector finds a different number of elements. The code is the same except for the assertions.

Desired behavior:

The same selector finds the same elements, regardless of chained assertions.

Steps to reproduce: (app code and test code)

This code:

describe("autocomplete", function() {
    var locationSearchBar = ".location-selector"
    var locationSearchField = ".select2-dropdown .select2-search__field"

    it("should display District and County results", function() {
      // ARRANGE
      cy.visit("https://www.imovirtual.com/comprar/apartamento/")
      // ACT
      cy.get(locationSearchBar).click()
      cy.get(locationSearchField).type("lisboa")
      // ASSERT
      cy.get("li.select2-results__option > div").should("contain", "Lisboa")
      cy.get("li.select2-results__option > div").should("contain", "(Distrito)")
    })
  })

Versions

macOS 10.14.4, Chrome 74, Latest Cypress

[dialex]

Right now I’m using a

cy.get(".loading-results").should("not.be.visible") // explicit wait

instead of the cy.wait() you suggested. Is that ok too? I prefer explicit waits.

[jennifer-shehane]

Yes, this seems to be the case. You may want to add a cy.wait() for the autosuggest XHR to finish before running the cy.get() to ensure the correct results are populated first.