test-coverage
Here are 95 public repositories matching this topic...
-
Updated
Aug 20, 2020 - JavaScript
-
Updated
Oct 2, 2020
-
Updated
Oct 26, 2020 - Ruby
-
Updated
Jul 13, 2020 - Python
-
Updated
Mar 22, 2020 - Go
Description
Like the old event reporter, move all the code that deals with crash reporting and sentry init into a new module.
This will help abstract away the knowledge of the crash capture to a single area.
Design
class CrashReporter
constructor(enableCrashReporting)
capture(error)
Existing Code
// Only send crash reports if the user al-
Updated
Oct 15, 2020 - JavaScript
-
Updated
Oct 26, 2020 - CMake
-
Updated
Dec 21, 2018 - Python
-
Updated
Oct 8, 2018 - Ruby
-
Updated
Dec 16, 2019 - Go
-
Updated
Oct 13, 2020 - Java
-
Updated
Oct 4, 2019 - Shell
-
Updated
Sep 4, 2020 - JavaScript
-
Updated
Mar 10, 2019 - PHP
-
Updated
Aug 9, 2019 - Kotlin
-
Updated
Jun 25, 2020 - Java
-
Updated
Apr 26, 2018 - C++
-
Updated
Oct 23, 2020 - Python
-
Updated
Feb 26, 2018 - Python
-
Updated
Aug 4, 2020 - Kotlin
-
Updated
Nov 17, 2018 - Java
-
Updated
Jul 31, 2020 - Python
-
Updated
Jun 3, 2020 - HTML
-
Updated
Nov 27, 2019 - Python
-
Updated
Oct 6, 2020 - HTML
-
Updated
Aug 6, 2020 - Python
Improve this page
Add a description, image, and links to the test-coverage topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the test-coverage topic, visit your repo's landing page and select "manage topics."


We have a problem: if files aren't loaded/required we don't have branch data. If they are added through
track_fileswe give it 0/0 branches which we show as 100% coverage (all possible branches are covered).That math is "wrong" though here because there are branches but we don't know what they are. We should probably count total branches here as "unkown" and establish that in our "math unive