Conversation
Vince-C156
left a comment
There was a problem hiding this comment.
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:
