-
Notifications
You must be signed in to change notification settings - Fork 16
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
add support for unittests (via pytest) #39
Comments
Thanks for the suggestion. As stated in the PR #38 I need to understand both sequence and objects that lies beneath. I'll put details about that here for clarity's sake. |
Will be waiting for unittest support ;) |
Hello I've been more busy than expected but I have been able to made some progress. However, I've found an interesting way of injection that seems promising. I'll try to dig in the next days. |
I managed to intercept the test function for each unittest. I can obtain measures which seems fine. Keep you posted. |
Dear @js-dieu, thank you for the great plugin! Would you mind to share your progress in a branch? This feature would help me a lot and maybe I can help with the progress. Regards Roman |
Follow up: It is working here outside of the pytest-monitor: https://github.com/ChaoticRoman/pytest-monitor-example/blob/custom_memory_profiler/unittestit.py |
Hello @ChaoticRoman I unfortunately lost the development after entering an erroneous command. That being said, I might be able to recode what I did, though your snippet is neat for starting it again. Keep you posted! |
Bloomberg guys just released this: https://github.com/bloomberg/memray Will check it out and let you know. |
Memray and pytest-memray looks cool but have this exactly same issue, reported: bloomberg/pytest-memray#6 |
As discussed here #38
pytest
almost fully supportsunittest
, but currentlypytest-monitor
skips allunittest
-based tests.I originally proposed to document this, but it was suggested that perhaps this can be fixed and
pytest-monitor
could supportunittest
-based tests too, which would be awesome.So as suggested opening this Issue to track the feasibility/progress on this front.
The text was updated successfully, but these errors were encountered: