Skip to content

more subtle ways to test constraints #7

Open
@mwotton

Description

currently, we recommend that there be a healthcheck endpoint that throws 500 if anything's broken. This is a barely-adequate stopgap for now: we probably want a way to pass in conditions that can access the full sequence of calls - something like certain routes always returning a 401 before authorisation occurs.

could look to https://hackage.haskell.org/package/servant-quickcheck-0.0.10.0 for inspiration here.

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