(uncaught exception) undefined: undefined

[titivermeesch]

Current behavior

Here is the test case that is failing:

it('can create a new equipment model', () => {
    cy.clickOnElementByText('Equipment Models')
    cy.clickOnElementByText('Add model')
    cy.pickElementFromSelect('cy|type', equipmentType, '.ant-select-item')
    cy.get('cy|brand').type(modelBrand)
    cy.get('cy|name').type(modelName)
    cy.get('cy|description').type('description')
    cy.get('cy|cost').type(300)
    cy.contains('OK').click()
    // cy.searchTable(modelName)
    // cy.checkElementContainsValue('.ant-table-tbody', modelName)
  })

My test was not like this originally but I've tried to narrow it down as much as possible (by using normal cypress commands instead of custom ones for example).

I keep getting this error:

Right now it's on the command pickElementFromSelect but it also happens on the cy.get ones, it seems like a very random behavior.

I'm not sure where it comes from. There are no other errors in the console during execution and the app just workes fine when I test it manually.

Is there a way to know where this comes from?

Desired behavior

The commands should just be executed.

Versions

• Using Chrome 90, but also saw this with Edge 90
• Cypress 7.3.0 (also had it on 7.2.0)
• MacOS 11.2.3 (It also happens in CI on Ubuntu 18.04.5)

Working versions

My tests seem to run fine on 6.5.0, but not on the latest version

[jennifer-shehane]

Yah, that's not a great error message to help tracking down. Could you provide the custom command code for the clickOnElementByText and pickElementFromSelect commands?

[titivermeesch]

Sure:

clickOnElementBySelect: text => cy.contains(text).click()
pickElementFromSelect:

(selector, valueToPick, waitForLoading = true) => {
  if (waitForLoading) {
    cy.get('[data-cy=type] > .ant-select-arrow > .anticon > [data-icon=loading]svg').should(
      'not.be.visible'
    )
  }

  cy.get(selector).click().type(valueToPick)
  checkElementExists('.ant-select-item-option')
  clickOnElement('.ant-select-item-option').first()
}

checkElementExists: selector => cy.get(selector).should('exist')
clickOnElement: selector => cy.get(selector).click()

The last ones were little helper functions, but the result is the same by just doing cy.get....

[jennifer-shehane]

@titivermeesch Yeah, I don't see anything in the custom commands that seems strange. Can you provide a reproducible example? A full test file that we can run and see this throwing the error? Thanks.

[titivermeesch]

I recently updated to v8.3.0 and I'm not experiencing this issue anymore. I guess it solved itself.

I'll reopen this issue if I manage to recreate the issue again

[Mona-Superscientist]

I'm facing a similar problem in my test with the last version of cypress.

[titivermeesch]

Having this as well with the latest version, had it as well with v8.3.0. I'm currently stuck at 6.5 because everything else seems to fail the tests instantly

[nullbytesoftware]

I am having similar issues in v10.4.0

This works (depricated):

cy.get('[data-testid="interruption-button-launch"]').then((el) => { el.click(); });

This does not:

cy.get('[data-testid="interruption-button-launch"]').click()

[ushashir]

I am having a similar issue with version 11.0.0

[geritol]

experiencing the same with version 11.2.0
I am getting (uncaught exception) undefined: undefined errors, on the cypress log, but the error is correctly displayed on the developer console. I think it happens when a promise throws an uncaught exception in the app while executing the test code

[geritol]

isolated a potentatial root cause with reproduction in: #24915

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[cypress-app-bot]

This issue has been closed due to inactivity.