GitXplorerGitXplorer
w

coverage_test_case

public
1 stars
0 forks
0 issues

Commits

List of commits on branch master.
Unverified
f88af6f76b779411ad8515bb8069af73c1455c1c

added readme for github

wwchristian committed 13 years ago
Unverified
188fa333669ab13303d10c25ad2ed19f9b815023

cut down coverage script to essentials

wwchristian committed 13 years ago
Unverified
b5c5e86fce108cd1c04b4806ccd64f4af8b4f536

added counter example in actual script that shows the code is covered when executed at runtime

wwchristian committed 13 years ago
Unverified
9ceef22759343c838aaee3060d3033f970adfc25

minimized module down to bare requirements to be visible, but uncovered, despite executing

wwchristian committed 13 years ago
Unverified
6f4b062f8d916d05734c4f5994ab65bffd56a89e

moved the module out of sub dir

wwchristian committed 13 years ago
Unverified
49a603de47a016298e794781ca75bc1cd3e16cfe

cut out more irrelevant code

wwchristian committed 13 years ago

README

The README file for this repository.

Coverage Gap Test Case

In this repo you will find a simple script that loads a module and then executes some code in its runtime. The runtime code is properly caught by D::C.

On the other hand, the module also executes some code, which however will end up being executed at compile time within the require call in the script file. That code is not recorded as covered, which happens, i assume, due to being at compile time. In fact, without the empty sub in the module it wouldn't even show up in the report.