You report a bug, we fix it, test it and release it
We reproduce every report, fix it, cover it with a test and release it. The order depends on how badly the bug blocks your work.
The path of a bug report
Every report goes through the same steps, so you always know where it stands.
- 1ReportYou email us or use the ticket system to say what happened. We only ask for what's missing to reproduce it.
- 2PriorityA bug that stops work gets picked up right away. Smaller ones join the queue by the agreed rules.
- 3Fix with a testWe reproduce the bug, fix it and add a test so it doesn't come back with the next change.
- 4Release and updateThe fix goes to production and you get a note on what caused it and what we changed.
Signs bugs wait too long
Reports get lost
No one to fix it
Fixes break something else
Users work around bugs
What you get with every report
The same way of working for small and big bugs.
Ticket system
Priorities
Regression test
Test environment
Root cause note
Monthly report
How we check the results
Every month we show how many reports came in, how long they waited and how many bugs came back.
- 1Reports per month
- 2Time from report to fix
- 3Bugs that came back
- 4Open reports
When the same bugs repeat, we propose fixing them at the source.
Common questions
Do you fix bugs in apps you didn't build?
Yes. We start with a short audit of the code and access, then take on reports.
How do I report a bug?
By email or in the ticket system. A description of what happened and a screenshot, if you have one, are enough.
What if a bug stops the business?
We take it on right away, outside the queue. The rules and response times go into the contract.
How do I know how long a fix took?
Each report has logged time, and the monthly report pulls it together.
Tell us what's broken
Let us know which app it is, what it's built with and which bugs happen most often. We reply within one business day.