Skip to content
This repository was archived by the owner on Jan 2, 2024. It is now read-only.
This repository was archived by the owner on Jan 2, 2024. It is now read-only.

Feat: Cypress best practices docs #107

@dhedgecock

Description

@dhedgecock

📝 Cypress guidelines

  • Prioritize stability - tests are only helpful when they are fast and reliable
  • Use mocks for interacting with the API -> it enables deterministic failures
    • ?What about "true acceptance" testing? -> Without stability tests aren't actually helpful.

The UI should be designed to gracefully handle API failures and data failures with appropriate alerting.

  • This makes the entire system faster and more robust
  • Self documenting in code
  • System level ownership

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions