BoringSSL maintains a suite of protocol tests for their TLS library [1]. We may be able to integrate and run these tests via a "shim" test runner that is provided a port as argument [2] . NSS has successfully integrated the BoringSSL tests. The difficult part here is identifying which tests to enable/disable to play nice with BoringSSL's test suite. For example, we'll want to disable anything DTLS related.
raycoll
commented
7 years ago
BoringSSL maintains a suite of protocol tests for their TLS library [1]. We may be able to integrate and run these tests via a "shim" test runner that is provided a port as argument [2] . NSS has successfully integrated the BoringSSL tests. The difficult part here is identifying which tests to enable/disable to play nice with BoringSSL's test suite. For example, we'll want to disable anything DTLS related.
[1] https://boringssl.googlesource.com/boringssl/+/master/ssl/test/ [2] https://boringssl.googlesource.com/boringssl/+/master/ssl/test/PORTING.md