On Feb 22, 2014, at 8:18, Kyle Huey <m...@kylehuey.com> wrote: > If you needed another reason to follow the style guide: > https://www.imperialviolet.org/2014/02/22/applebug.html >
Code coverage would have caught this as well. The time investment into 100% line and branch coverage is debatable. But you can't argue that code coverage has its place, especially for high-importance code such as crypto. AFAIK, our automation currently does not collect code coverage from any test suite. Should that change? Possibly radical idea: patches are automatically audited to verify tests actually test the new/changed code. If not, a giant flag is raised and reviewers can act accordingly. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
