Difference between revisions of "Code Coverage Tool for R"

From R Consortium Wiki
Jump to: navigation, search
Line 3: Line 3:
 
Code coverage helps to ensure greater software quality by reporting how thoroughly test suites cover the various code paths. Having a tool that supports the breadth of the R language across multiple platforms, and that is used by R package developers and R core teams, helps to improve software quality for the R Community. While a few code coverage tools exist for R, this Oracle-proposed ISC project aims to provide an enhanced tool that addresses feature and platform limitations of existing tools via an ISC-established working group. It also aims to promote the use of code coverage more systematically within the R ecosystem.
 
Code coverage helps to ensure greater software quality by reporting how thoroughly test suites cover the various code paths. Having a tool that supports the breadth of the R language across multiple platforms, and that is used by R package developers and R core teams, helps to improve software quality for the R Community. While a few code coverage tools exist for R, this Oracle-proposed ISC project aims to provide an enhanced tool that addresses feature and platform limitations of existing tools via an ISC-established working group. It also aims to promote the use of code coverage more systematically within the R ecosystem.
  
ISC Proposal Document
+
Github project: https://github.com/jimhester/covr/issues
 
+
Meeting Minutes
+
  
 
=== Working Group Members ===
 
=== Working Group Members ===
Line 21: Line 19:
 
* Qin Wang, Oracle
 
* Qin Wang, Oracle
 
* Hadley Wickham, RStudio – ISC Sponsor
 
* Hadley Wickham, RStudio – ISC Sponsor
 +
 +
=== Status as of October 4, 2016 ===
 +
* Branch coverage with profile stats – in progress
 +
* Define canonical performance benchmark suite – in progress
 +
* #144 store test results as well as coverage – in progress
 +
* #134 ICC compatibility – TESTS COMPLETE
 +
* Make code coverage use more pervasive in R community – in progress
 +
* Correct behavior for parallel code execution – DONE
 +
* Resolve package dependency license issues – DONE
 +
* #174 R6 methods are not covered - DONE
 +
* #117 covr with a local jenkins builder – DONE
 +
* #99 Shiny Source Tab Indicate the Filename – DONE
 +
* Observations testing ORE with covr – DONE
 +
 +
=== Meeting History ===
 +
* October 4, 2016
 +
* September, 22, 2016
 +
* September 8, 2016
 +
* August 18, 2016
 +
* July 28, 2016
 +
* July 7, 2016
 +
* June 16, 2016
 +
* June 2, 2016
 +
* May 24, 2016
 +
* May 15, 2016

Revision as of 20:02, 18 October 2016

Working Group: Code Coverage Tool for R

Code coverage helps to ensure greater software quality by reporting how thoroughly test suites cover the various code paths. Having a tool that supports the breadth of the R language across multiple platforms, and that is used by R package developers and R core teams, helps to improve software quality for the R Community. While a few code coverage tools exist for R, this Oracle-proposed ISC project aims to provide an enhanced tool that addresses feature and platform limitations of existing tools via an ISC-established working group. It also aims to promote the use of code coverage more systematically within the R ecosystem.

Github project: https://github.com/jimhester/covr/issues

Working Group Members

  • Shivank Agrawal, Oracle
  • Chris Campbell, Mango Solutions
  • Santosh Chaudhari, Oracle
  • Karl Forner, Quartz Bio
  • Jim Hester, RStudio
  • Mark Hornick, Oracle – Group Leader
  • Chen Liang, Oracle
  • Willem Ligtenberg, Open Analytics
  • Andy Nicholls, Mango Solutions
  • Vlad Sharanhovich, Oracle
  • Tobias Verbeke, Open Analytics
  • Qin Wang, Oracle
  • Hadley Wickham, RStudio – ISC Sponsor

Status as of October 4, 2016

  • Branch coverage with profile stats – in progress
  • Define canonical performance benchmark suite – in progress
  • #144 store test results as well as coverage – in progress
  • #134 ICC compatibility – TESTS COMPLETE
  • Make code coverage use more pervasive in R community – in progress
  • Correct behavior for parallel code execution – DONE
  • Resolve package dependency license issues – DONE
  • #174 R6 methods are not covered - DONE
  • #117 covr with a local jenkins builder – DONE
  • #99 Shiny Source Tab Indicate the Filename – DONE
  • Observations testing ORE with covr – DONE

Meeting History

  • October 4, 2016
  • September, 22, 2016
  • September 8, 2016
  • August 18, 2016
  • July 28, 2016
  • July 7, 2016
  • June 16, 2016
  • June 2, 2016
  • May 24, 2016
  • May 15, 2016