You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New modals logic do not require hiding "exit" button from onboarding if device is not ready to work with.
It also somewhat mitigates #1046 Seems like if there are less renders, the chance it happens is smaller.
New modals logic do not require hiding "exit" button from onboarding if device is not ready to work with.
It also somewhat mitigates #1046 Seems like if there are less renders, the chance it happens is smaller.
* onboarding exit button always visible
New modals logic do not require hiding "exit" button from onboarding if device is not ready to work with.
It also somewhat mitigates #1046 Seems like if there are less renders, the chance it happens is smaller.
* less unit test-like approach
acting like unit writing unit tests is considered antipattern, see here https://docs.cypress.io/guides/references/best-practices.html#Creating-%E2%80%9Ctiny%E2%80%9D-tests-with-a-single-assertion other way round it gives us performance boost
* clean up onboarding tests
This is reported in cypress repo cypress-io/cypress#5743
Started to appear after we upgraded to Cypress 3.7.0. Appears only on local test run, does not affect CI.
This is a common error covered by Cypress documentation, https://docs.cypress.io/guides/references/error-messages.html#cy-failed-because-the-element-you-are-chaining-off-of-has-become-detached-or-removed-from-the-dom
but I believe that we are not the case mentioned there. We use cy.get().click() directly one after another.
TODO:
test if update to 3.8.1 (latest) helpsdoes not helpThe text was updated successfully, but these errors were encountered: