-
Updated
Nov 1, 2020 - JavaScript
unittest
Here are 978 public repositories matching this topic...
-
Updated
Nov 5, 2020 - TypeScript
-
Updated
Sep 29, 2020 - Swift
Hello, and thank for this module.
I am wondering if consideration has been given to adding colour to the stack traces printed out upon failure of a test. For a test runner emphasizing colour, this seems like an obvious omission. I have patched in this functionality using pygments in my fork: psacawa/green@1922bc8 in an ad hoc fashion t
-
Updated
Sep 19, 2020 - Python
-
Updated
Oct 26, 2020 - Python
-
Updated
Nov 4, 2020 - C#
-
Updated
Jul 7, 2020 - Python
-
Updated
Nov 30, 2018 - Python
-
Updated
Sep 2, 2020 - Python
-
Updated
Apr 28, 2020 - Go
-
Updated
Oct 20, 2020 - Python
-
Updated
Mar 22, 2020 - Go
-
Updated
Oct 3, 2020 - C#
-
Updated
Jun 19, 2020 - Python
-
Updated
Sep 13, 2020 - Python
-
Updated
Sep 11, 2020 - Shell
-
Updated
Nov 5, 2020 - Lua
-
Updated
Nov 28, 2017 - Kotlin
-
Updated
Oct 5, 2020 - D
Improve this page
Add a description, image, and links to the unittest topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the unittest topic, visit your repo's landing page and select "manage topics."
It would be helpful if the lcov generated reports could generate relative paths. My use case is that I am generating coverage reports from a docker image and then using VS Code Coverage Gutters which supports relative paths to view the coverage. But it doesn't work because the absolute paths on the docker c