Remove extra work when computing code coverage
See original GitHub issuehttps://github.com/facebook/buck/commit/0cc8d5d6a9629b56f49dee41e9d2623058337380 introduced a performance degradation for projects that do not use the direct_to_jar
spool mode when computing code coverage
Ideally, the classes dir can be used if it already exists to prevent unzipping for projects that output classes to the filesystem already.
Issue Analytics
- State:
- Created 7 years ago
- Comments:17 (9 by maintainers)
Top Results From Across the Web
Code coverage testing - Visual Studio (Windows)
Learn how to use the code coverage feature of Visual Studio to determine what proportion of your project code is being tested by...
Read more >Improve Code Quality Using Test Coverage - CODE Magazine
In this article, I'll introduce the concept of code coverage by exploring the value of measurements such as statement coverage, ...
Read more >Code Coverage Tutorial: Branch, Statement, Decision, FSM
Branch coverage method removes issues which happen because of statement coverage testing; Allows you to find those areas which are not tested by ......
Read more >How do I increase my code coverage, or why can't I cover ...
1 Answer 1 ... Code coverage is a measurement of how many unique lines of your code are executed while the automated tests...
Read more >Clear code coverage information in IntelliJ - Stack Overflow
just close the coverage window with "x" button: closing window. update: for the recent IntelliJ IDEA 2018.2.x, you can hide coverage by clicking...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@tdrhq We are seeing an exception with the latest buck version
This seems to be fixed with
jar_spool_mode = direct_to_jar
in the buckconfig file