Support and Maintenance en Austin
How we work in Austin
The flaky test teaches people to ignore alerts
It falls one run in twenty for no visible reason, so people run it again and carry on. The damage is not that one test: it is the habit of hitting retry. Weeks later a genuine failure gets the same treatment and walks past three people.
A flaky test gets fixed or gets deleted
There is no third way, though the third way is what everybody practices. It comes off the critical path, it gets a date, and if that date arrives unfixed it goes. A suite with fifteen doubtful tests inside is worth less than the same suite with fifteen tests fewer.
Every fault leaves its test written before the fix
The order is not a whim: first you reproduce the failure in a test that actually fails, and only then you fix it until you watch it pass. That way you know the fix fixes and that this particular defect does not come back. It is the only coverage that grows for a reason and not for a quota.
Dependency updates come in through the same door
Bumping a library with nothing to verify it is shipping blind. With the suite in front, the proposal opens on its own, runs and arrives green or red. What used to be a risky afternoon every six months becomes a short spell every week.
Answering your questions
What people ask us about Support and Maintenance in Austin.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Support and Maintenance: stack, process, use cases and FAQs