[HN Gopher] Pytest-austin: performance regression testing with n... ___________________________________________________________________ Pytest-austin: performance regression testing with no instrumentation Author : p403n1x87 Score : 25 points Date : 2020-10-22 19:29 UTC (3 hours ago) (HTM) web link (github.com) (TXT) w3m dump (github.com) | JackC wrote: | Has anyone used something like this to report performance | regressions? I don't as much want to assert that performance | stays below X seconds on particular tests, and more want a report | on pull requests if any tests regressed more than X%, the same | way I currently get CI reports for coverage regressions. | p403n1x87 wrote: | That's a good idea and planned for the next release. | achamayou wrote: | https://github.com/jumaffre/cimetrics | miohtama wrote: | I hope TypeScript community will come up with something as | powerful as py.test soon. Fixtures keep your wrists agony free | when writing tests. Asserts are joy to read. Decorators make | everything readable. Plugin system has a solution for everything. | | Meanwhile in the JS land | I.cannot().keep.guessing().what().crap().to.chain.or.not(). | nunez wrote: | pytest is awesome, but I wish pytest were more like rspec. In | my opinion, rspec is THE BEST testing framework out there. | LiamPa wrote: | Yesterday I was wondering if anything like this existed after | accidentally adding 100 duplicate database requests on a Django | endpoint. | JackC wrote: | django_assert_num_queries is helpful for this as well -- | basically any time I'm writing a test for something where I've | spent time thinking about query efficiency in the first place, | I'll throw in an assert. (I actually use a homerolled version | that can log the location of the queries with -v, but same | idea.) | | https://pytest-django.readthedocs.io/en/latest/helpers.html#... ___________________________________________________________________ (page generated 2020-10-22 23:00 UTC)