-
Notifications
You must be signed in to change notification settings - Fork 0
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 pytest benchmarking extension #3
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Considering this is solely for unit testing, maybe all the requirements should be within a single requirements.txt. Also for the statistics in the screenshots you provided please add to the readme how you got these statistics and the machine you ran it on. It would be a good idea for these specs to displayed after every test. I was also not able to successfully run the test script without errors. I installed both requirements.txt and requirements-test.txt.
t depending on whos running it.
The reason I put the normal requirements and testing tools in different |
Good point, we should be documenting exactly what systems we've got this working on. I added a line on the project root README about this. |
Failed tests not merging. |
This lets us view the time it took to complete certain function calls. Activating the benchmarks doesn't require anything besides installing the extension and running the tests normally, and the output looks like this: