Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

coveragepy coverage of trace functions #547

Open
nedbat opened this issue Jan 1, 2017 · 0 comments
Open

coveragepy coverage of trace functions #547

nedbat opened this issue Jan 1, 2017 · 0 comments
Labels
enhancement New feature or request

Comments

@nedbat
Copy link
Owner

nedbat commented Jan 1, 2017

Originally reported by Loic Dachary (Bitbucket: dachary, GitHub: dachary)


The code in tracer.c, pytracer.py, or code in control.py called from those does not show as covered when running make metacov. Using mocks would be tedious and error prone.

The code could run with a trace function that captures the sequence of events, and frames. Then replay those against the code. The problem is, you can't just capture the events, you have to actually send them to the real trace function also, and if that function has state, like whether a file has been should_trace'd already or not, then it's hard to replay the events.


@nedbat nedbat added trivial enhancement New feature or request labels Jun 23, 2018
@nedbat nedbat removed the 4.3 label Aug 17, 2018
@nedbat nedbat removed the trivial label Aug 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant