You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
since we have the %cell injection, I would think all we need to do is maintain a map of nb line # to test line #, inject coverage.py into the test itself, then match back the covered line using the mapping.
@timkpaine The nbval coverage is all about getting coverage data in python modules, from the execution of the notebook. It doesn't currently attempt to measure coverage in the notebook. The problem is that coverage will not be available in the same scope as the coverage gathering was started, i.e. the notebook global scope. There might be a clever work-around somehow, but I haven't dived deep enough into it to find anything.
Current cell coverage
(num cells tested)/(num cells)
is a proxy for actual coverage.nbval includes a coverage measure - should investigate that.
Current coverage is relatively easy to fake, e.g.
Something related to "what actually ran?" (e.g. detection that cell source was submitted to kernel) might be better than a static check.
The text was updated successfully, but these errors were encountered: