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

Discuss if hunter should run previous tracer #64

Open
ionelmc opened this issue Jun 1, 2019 · 1 comment
Open

Discuss if hunter should run previous tracer #64

ionelmc opened this issue Jun 1, 2019 · 1 comment

Comments

@ionelmc
Copy link
Owner

ionelmc commented Jun 1, 2019

Currently hunter only reinstalls previous tracer.

It could run the previous tracer as well - this would allow running stuff with coveragepy and not have coverage data gaps wherever you had hunter on.

However, this would be problematic if you start multiple hunter tracers like in #59 (comment)

@tshead2
Copy link

tshead2 commented Dec 5, 2024

Not sure if this is what I want, or if this is the right place to ask, but here goes: when I run my regression test suite, I use pycoverage and behave, along the lines of:

$ coverage run -m behave

... which run my testing code. When that testing code invokes hunter.record(..., action=MyAction), MyAction never actually gets called. Are there any tricks to get hunter to work in this context?

Thanks in advance,
Tim

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants