QA engineer based in Hove, UK. I build open-source Python tools for testers, mostly around pytest and the everyday problems of API and integration testing: brittle test data, slow suites, and the gap between the tools teams already use (Postman, Kibana) and proper test code.
| Project | What it does |
|---|---|
postman2pytest  |
Convert Postman v2 collections into runnable pytest suites: auth headers, env vars, parametrised fixtures. |
secure-log2test  |
Generate pytest regression tests from anonymised Kibana log exports, with PII redacted by default. |
| pytest-conversational | pytest plugin for deterministic multi-turn dialogue testing. No LLM dependency. |
| phoenix2pytest | Turn production LLM failures into regression tests, automatically. |
| pytest-resilience-agent | Auto-generate resilience tests for LLM apps from a Lark grammar. |
| flaky-detector-agent | Detect flaky tests from CI history and propose fixes. |
- HackerNoon: Turn your Postman collection into pytest tests with one command. How postman2pytest came together.
- HackerNoon: Turn Kibana logs into pytest cases without leaking secrets. The design behind secure-log2test, including its redaction layers.
- Habr (RU): postman2pytest and secure-log2test.
- Dev.to: Postman and pytest are living in parallel universes. Here is a bridge. Also cross-posted on Medium and Hashnode.
Sole QA on backend e-commerce. I own API testing across 12+ Postman collections plus a regression suite of 200+ cases, and I maintain an internal Selenium and pytest framework (POM) that other testers on the team picked up from our git. Most of my time goes into root cause analysis with Grafana, Kibana and SQL, and into cutting down flaky tests so they stop costing the team momentum.
I also chime in on pytest-dev GitHub Discussions now and then. Found a real bug in any tool above? Opening an issue is the fastest way to my attention.