Skip to content

Retry-ability #117

@badeball

Description

@badeball

Hi,

Retry-ability is a core feature of Cypress and part of what makes it so usable. Cypress also provides APIs to create custom commands that adhere to this pattern (using cy.should with functions, which is retried for you).

At my current project, we have some visual regression tests testing something with a very minor animation. We've successfully stored baseline images, but experience intermittent failures (0.3% - 0.5%) due to this animation.

I think it would be very cool for this library to do retry-ability, like we're all used to Cypress doing. I don't think it should be more than changing a .then with a .should, and using expect instead of throwing.

What do you think of this?

One challenge that does come to mind is when to store baseline images in scenarios with animations. This isn't however a new scenario, but something that is already difficult today as well.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions