Closed Bug 970470 Opened 6 years ago Closed 6 years ago
Clarify and expand (if needed) certificate EKU processing tests
keeler noted that the EKU processing in insanity::pkix, CheckExtendedKeyUsage, is subtle and that we should make sure we have good test coverage. We actually have "pretty good" test coverage for this with test_certificate_usages.js, test_intermediate_basic_usage_constraints.js, etc. Those tests have helped me find multiple bugs and incompatibilities when doing the initial insanity::pkix implementation. However, it is difficult to map those tests to the implementation and to the spec, and that means it is unclear what exactly the test coverage is. Since the time those tests were written, we've increased our testing framework and testing style substantially. We should redo the EKU testing to make it clearer that we have "complete" test coverage.
98% addresses on landing of tests for https://bugzilla.mozilla.org/show_bug.cgi?id=982314. Consider solved?
(In reply to Camilo Viecco (:cviecco) from comment #1) > 98% addresses on landing of tests for > https://bugzilla.mozilla.org/show_bug.cgi?id=982314. Consider solved? I think you meant to reference a different bug than bug 982314. It would be good to hear from keeler about whether he is satisfied with the test coverage for EKU processing, since I originally filed this bug based on his concern that not enough was being tested.
As I understand them, the tests added in bug 982292 test the functionality I was concerned about here.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 982292
You need to log in before you can comment on or make changes to this bug.