I will debug and fix one failing unit test in your repository


About this gig
I will reproduce the failing test locally using your repo or provided archive, apply the smallest safe code or test correction required to restore the test to passing, and deliver patched files, a short root-cause summary, and an optional PR. This gig is designed for quick CI breaks, small regressions, and deterministic unit-test fixes where the failure is reproducible without full infrastructure-level access. I avoid large refactors and scope creep; changes are documented and explained so you can review or revert confidently.
This gig delivers:
- Patched source file(s) and, if necessary, an updated/clarified test file.
- A short root-cause note (26 sentences) explaining the failure and the remediation.
- Exact reproduction command and passing pytest output snippet.
- Optional: a PR created against your branch or a unified diff/patch file.
Get to know Mars M
Jack of all trades, doctor of one
- FromUnited States
- Member sinceSep 2024
- Avg. response time1 hour
Languages
English, French, Spanish
My Portfolio
FAQ
Will you refactor unrelated code?
No. I will make the minimal, well-documented change required to fix the failing test.
Do you fix flaky tests?
This gig is scoped to deterministic failures with a reproducible test case. Flaky-test diagnosis is a separate gig.
Can you push to my repo?
Yes — provide write access or request a PR/patch; specify workflow when ordering.
What if reproduction fails on my side but passes for you?
I will include the environment and commands I used; if environment differences remain, you can purchase the CI integration or a longer debugging session.
Do you change tests or production code?
I prefer fixing production code; I will only change tests when they are demonstrably incorrect, and the minimal test modification is safer than changing production behavior.
What does the regression test include?
A single, targeted test that ensures the specific bug you hired me to fix cannot silently reappear. It’s not a full test-suite expansion — it’s a guardrail for the exact failure you experienced.
Will you work on non-Python repositories?
Yes — I am happy to work in non‑Python repos. I’m comfortable navigating most codebases, but my strongest languages are Python, JavaScript, TypeScript, Rust, and Unix automation (bash). I’m happy to review anything and let you know what I can contribute.
