Alternatives
Products that do what Pytest-scrutinize – find bottlenecks in your test suite does
- 1SP
2017 · github.com
- 2PS
2018 · github.com
- 3KD
2017 · k6.io
- 4DF
2019 · github.com
- 5WB
Hi, we are working on a tool for speeding up test runs, by skipping tests unaffected by code changes. Effectivly, Saving 80-95% of the time, by skipping 80-95% of tests. We started a few months ago, and have managed to get into a few production CI systems. All our prospects and users are on holiday right now. So we decided to repackage and open-source for local test running. available here (https://github.com/nabaz-io/nabaz) under MIT license. One line change: pytest -v -> nabaz test --cmdline "pytest -v" Stalk us on GitHub, or just Star us. Ask questions, we'll answer in…
2022 · github.com
- 6AT
2017 · github.com
- 7FH
2023 · product.distoai.com
- 8SA
I've frequently found myself using [nvitop](https://github.com/XuehaiPan/nvitop) to diagnose GPU/CPU contention issues. The two best things about it are: - It's easy to install if I can access pip in the container - It makes a compelling screenshot (which helps me communicate with coworkers.) With those two lessons in mind: Here is Sping! Purpose: Help observe and diagnose latency issues at layer 4+ (TCP/HTTP/HTTPS) Two good things about it: - It's easy to install if you have pip. (Available at…
2025 · dseltzer.gitlab.io
- 9LD
Hi HN! We’re Adrien and Kanav. We met at our previous job, where we spent about a third of our lives combating a constant firehose of bugs. In the hope of reducing this pain for others in the future, we’re working on automating debugging. We’re currently working on a platform that ingests logs and then automatically reproduces, root causes and ultimately fixes production bugs as they happen. You can see some of our work on this here - https://news.ycombinator.com/item?id=39528087 As we were building the root-cause phase of our automated debugger, we realized that we developed…
2024 · github.com
- 10IB
I got sick of the old software development loop: Change code -> Run tests -> wait -> wait some more -> look at failures. I decided to build a tool that will enable you to: Change code -> look at failures. No wait time, no explicit test running. Under the hood: - Runs the whole test suite and collects code coverage per test. - For each auto file save, analyzes the changes on the tests. - Runs changed tests in the background. - Display results, the loop time from change to test results is approx 250ms. Instead of: code -> alt+tab -> arrow up -> rerun all the tests -> wait ... -> test results…
2022 · github.com
- 11AF
2015 · github.com
- 12RO
2017 · github.com
- 13LR
2017 · loadmill.com
- 14PS
2020 · pyrustic.github.io
- 15PC
2017 · github.com
- 16IM
I built BuzzBench because I was frustrated with how complex performance testing tools have become. And I was ending up writing my own scripts to test endpoints and manually check out resource usage at the time of testing. Checkout demo: https://www.youtube.com/watch?v=yAnbZMoQvmQ
2025 · buzzbench.io
- 17BA
2015 · github.com
- 18BA
2014 · bernoulli.io
- 19KA
I built this because Cursor, Claude Code and other agentic AI tools kept giving me tests that looked fine but failed when I ran them. Or worse - I'd ask the agent to run them and it would start looping: fix tests, those fail, then it starts "fixing" my code so tests pass, or just deletes assertions so they "pass". Out of that frustration I built KeelTest - a VS Code extension that generates pytest tests and executes them, got hooked and decided to push this project forward... When tests fail, it tries to figure out why: - Generation error: Attemps to fix it automatically, then tries again -…
Jan 2026 · keelcode.dev
- 20PW
2021 · github.com
- 21SC
2015 · github.com
- 22PD
2012 · proglipsum.com
- 23KP
2021 · github.com
- 24IA
2018 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →