BullseyeCoverage vs gcovr
BullseyeCoverage
bullseye.comgcovr
gcovr.comSide by side
| Figure | BullseyeCoverage | gcovr |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | Yes | — |
| Open source | — | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 2 | 0 |
| Spec score · Test Coverage Tools | 8.5 (#4) | 7.6 (#13) |
| Operating systems | The company lists Windows, Linux desktop and server, macOS, and embedded systems as supported environments. | The project supports Linux, Windows, and macOS. |
| Purpose | BullseyeCoverage measures C and C++ code coverage to help find untested code and assess testing completeness. | gcovr manages GNU gcov and generates summarized code coverage results. |
| Support | The company says technical support is included with every purchase and provides a technical support request form. | The project directs users to GitHub issue tickets, Stack Overflow and a Gitter chat room for help. |
Plans
BullseyeCoverage
- Evaluation licenseFree
- BullseyeCoverage licensePrice not published
In their own words
BullseyeCoverage
BullseyeCoverage measures C and C++ code coverage to help developers and testers locate untested code and assess testing completeness. It provides function coverage and condition/decision coverage, and results can be viewed interactively in Coverage Browser or generated as reports. Listed outputs include HTML, text, annotated source code, XML, Cobertura, and CSV. The tool instruments C and C++ source code and supports standard C++ versions from C++98 and C versions from C90 through current versions, plus compiler extensions. Coverage data can be exported in XML or CSV, and results from multiple computers can be merged. Supported tools include Visual Studio, Clang, GCC, Xcode, CMake, Eclipse, and embedded development tools such as Code Composer Studio. Supported environments include Windows, Linux desktop and server, macOS, and embedded systems. The company reports that instrumented execution takes 1.3–1.9× longer and code and data size increase to 1.4×; build-time effects vary by compiler. A temporary, fully functional evaluation license costs nothing and expires at the end of its evaluation period. The perpetual paid license has no listed price.