e9cc4e4d75
They only seem to occur during testing at the moment. If we get a user report, we can investigate, but until then they're a distraction.
32 lines
1.0 KiB
JavaScript
32 lines
1.0 KiB
JavaScript
// ***********************************************************
|
|
// This example support/index.js is processed and
|
|
// loaded automatically before your test files.
|
|
//
|
|
// This is a great place to put global configuration and
|
|
// behavior that modifies Cypress.
|
|
//
|
|
// You can change the location of this file or turn off
|
|
// automatically serving support files with the
|
|
// 'supportFile' configuration option.
|
|
//
|
|
// You can read more here:
|
|
// https://on.cypress.io/configuration
|
|
// ***********************************************************
|
|
|
|
// Import commands.js using ES2015 syntax:
|
|
import './commands';
|
|
|
|
// Alternatively you can use CommonJS syntax:
|
|
// require('./commands')
|
|
|
|
Cypress.on('uncaught:exception', err => {
|
|
// Rapidly cy.visiting pages seems to cause an uncaught exception. This seems
|
|
// to be a testing artifact, since users can't click fast enough to cause this
|
|
// (to our knowledge).
|
|
if (err.name === 'ChunkLoadError') {
|
|
return false;
|
|
}
|
|
// We are still interested in other errors.
|
|
return true;
|
|
});
|