Skip to content

Investigate use of assertions during tests #418

Open
@ionut-arm

Description

@ionut-arm

It's worth looking into whether there could be any mechanisms by which we can instrument the service code to make it more obvious if something is wrong. For example, we could use assert! (which gets disabled/removed from release code, as @hug-dev has noted) to verify that data has the correct format etc. throughout our providers/authenticators.

Metadata

Metadata

Assignees

No one assigned

    Labels

    code healthIssues concerning overall code quality, safety and best practicemediumEffort labelsecurityIssues related to the security and privacy of the servicetestingTask related to testing

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions