OpenCppCoverage/OpenCppCoveragePlugin

Issues

• Add support for relative paths in settings

  #57 opened 3 years ago by danielschenk
  1

• Support Visual Studio 2022

  #48 opened 4 years ago by isalo
  7

• Plugin fails to install

  #56 opened 3 years ago by dingetje
  6

• Visual Studio 2022 Support

  #55 opened 3 years ago by TEMSSemi
  1

• Removing the "Press any key to continue" prompt?

  #14 opened 6 years ago by ocornut
  6

• Using this plugin in vs2019, the aligned "}" in the if else statement is not marked as covered

  #52 opened 3 years ago by wang321123
  0

• It would be nice to be able to run multiple test programs and get the union of the coverage.

  #40 opened 5 years ago by BengtGustafsson
  1

• Option to filter out specific files from the report.

  #47 opened 4 years ago by rawatlax
  0

• System.OutOfMemoryException when opening the settings window

  #46 opened 4 years ago by Justin-Randall
  0

• Need Functionality to save code coverage reports.

  #45 opened 4 years ago by rawatlax
  1

• Support Visual Studio 2022 Preview

  #44 opened 4 years ago by netmonitoring
  0

• Display coverage not working for all files

  #43 opened 4 years ago by RDols
  0

• didn't work for unittest project in visual studio 2015

  #42 opened 5 years ago by Jedcheen
  0

• Checkbox to group test programs to run and get coverage results merged

  #41 opened 5 years ago by BengtGustafsson
  1

• Unable to populate OpenCppCoverage Settings dialog

  #38 opened 5 years ago by claremacrae
  1

• Plugin doesn't work for static libraries

  #31 opened 6 years ago by samnaction
  2

• OpenCppCoveragePlugin doesn't show up in Build menu after installing the extension. Visual studio express 2017

  #39 opened 5 years ago by SaranshSaxena27
  0

• Double clicking required to activate buttons and checkboxes

  #28 opened 7 years ago by michalfita
  4

• Subsequent invocations of the plugin should remember previous settings

  #17 opened 6 years ago by bert8128
  7

• Feature request: Show results from cov-file without test again

  #35 opened 6 years ago by fgrz
  5

• System.ArgumentNullException when use GIT-compare

  #33 opened 6 years ago by fgrz
  2

• Visual studio 2015 gets hang some time while opening Settings window.

  #30 opened 6 years ago by vkpatel186
  1

• module matches no selected pattern (Visual Studio 2017 & gtest)

  #36 opened 6 years ago by Haqiverse
  2

• GUI: Scaling

  #34 opened 6 years ago by fgrz
  1

• Code coverage for ATL Projects (DLLs)

  #32 opened 6 years ago by cbigurra
  6

• Make it available for Visual Studio 2019

  #29 opened 6 years ago by michalfita
  10

• Settings-Filter not restore

  #27 opened 6 years ago by seungyongshim
  2

• Exception while executing Test-> Run CppCoverage

  #18 opened 7 years ago by g-glowacki
  2

• Error when opening the settings window.

  #11 opened 6 years ago by maxklint
  8

• VS2017 Community Cast Exception

  #26 opened 6 years ago by leleftheriades
  2

• How can I set excluded_line_regex?

  #25 opened 6 years ago by joseAndresGomezTovar
  2

• Xaml parsing error when opening plugin window in 0.9.6.0, VS 2017

  #23 opened 7 years ago by er2er
  1

• 0.9.6.0 Stopped working visual studio 2015

  #24 opened 7 years ago by rafae11
  1

• 'CoverageData.cs' could not be found.

  #19 opened 7 years ago by hsandt
  9

• Coverage and Settings panels should respect the color theme

  #16 opened 7 years ago by jornb
  3

• Run CppCoverage context menu is too in your face!

  #15 opened 7 years ago by mydeveloperday
  2

• Code is not selectable in editor

  #13 opened 7 years ago by mydeveloperday
  2

• Plugin fails to execute on VS2017 Community Edition

  #21 opened 7 years ago by MattRyder
  3

• Cannot run with Visual Studio Professional 2013

  #20 opened 7 years ago by Hajsen
  0

• Error "Item has already been added. Key in dictionary: 'Path' Key being added:" when using VS plugin

  #8 opened 8 years ago by kblunde
  4

• Get Error by creating

  #7 opened 8 years ago by ManX070
  1

• 32-/64-Build different information

  #6 opened 8 years ago by ThirtySomething
  2

• No full coverage

  #5 opened 8 years ago by ThirtySomething
  3