Ned Batchelder

*Original comment by* **Remi Rampin (Bitbucket: [remram44](https://bitbucket.org/remram44), GitHub: [remram44](https://github.com/remram44))** ---------------------------------------- I'm working on this in [pull request 27](https://bitbucket.org/ned/coveragepy/pull-request/27/263-treeview-for-html-report/diff).

There is still no tree view in the HTML report, no.

It doesn't look like wiki updates are in the GitHub GraphQL API, so it might be awkward. They also aren't in the REST API, so the information would have to...

@vincent-lg thanks for the detailed information. I'm familiar with these ideas, but have not done a good job carrying them through into the coverage report. Definitely we can add information...

Thanks, I appreciate any help. If you have solutions, we don't need to make separate issues, the pull requests will be a fine start.

*Original comment by* **Thomas Pansino (Bitbucket: [tpansino](https://bitbucket.org/tpansino), GitHub: [tpansino](https://github.com/tpansino))** ---------------------------------------- Any feedback here? I'd like to work on this in my spare time as a contribution to the community, but...

*Original comment by* **Thomas Pansino (Bitbucket: [tpansino](https://bitbucket.org/tpansino), GitHub: [tpansino](https://github.com/tpansino))** ---------------------------------------- Ok, I've played around with `coverage.py`'s reporting, and I think I have an initial idea I can show. Here is...

*Original comment by* **d (Bitbucket: [desmaj](https://bitbucket.org/desmaj), GitHub: [desmaj](https://github.com/desmaj))** ---------------------------------------- There are condition / decision coverage report examples in the instrumental docs [here](http://instrumental.readthedocs.io/en/latest/usage.html#condition-decision-coverage). I think it would be straightforward to incorporate...

*Original comment by* **Thomas Pansino (Bitbucket: [tpansino](https://bitbucket.org/tpansino), GitHub: [tpansino](https://github.com/tpansino))** ---------------------------------------- > Generally, behavior within a line is not visible to coverage.py, since the Python trace function works on a line-by-line...

@tpansino I haven't thought about how hard it would be to implement something like this. Generally, behavior within a line is not visible to coverage.py, since the Python trace function...