Skip to content

Self-test / map between rustls / CryptoProvider Validaton / Tests #31

@pinkforest

Description

@pinkforest

In ideal world rustls would cover a lot of the test cases - that are usable for provider validation

Need to map what can be re-used and then plumbed into here to validate in CI in lock-step with rustls releases

And what are missing and could be also perhasps upstreamed

Self-test aims to do simple integration test but could we also do test here utilsing upstream test suite w/o downstream deps / external connectivity ?

I'm working on this atm

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions