“The assessment on our billing service found duplicate mocks masking a VAT calculation branch. Pairing sessions were dense—I wished we had scheduled them earlier in the sprint—but the backlog tickets were clear enough for juniors.”
Client stories
Names and sectors are used with permission. Details are trimmed where NDAs apply, but the constraints and outcomes are real.
“Flaky diagnosis took six days, not five, because our staging data was a mess. SignalCrest documented that upfront and stopped at the agreed cap instead of padding hours.”
“Pipeline review cut our main branch wait from 38 to 22 minutes by splitting integration packs. We still need to tackle database fixtures, which they flagged but did not have scope to fix.”
Extended note: Western Cape health booking API
A twelve-person squad maintained pytest coverage above 80% while manual nurses still found slot double-bookings. SignalCrest mapped branch coverage on conflict-resolution modules and discovered tests asserting HTTP 200 without checking response bodies.
Over two weeks we added contract tests against the SMS gateway stub, rewrote three fixtures that shared database state, and left a heat map pinned in Confluence. Releases now include a coverage diff comment on each pull request—something their lead said they should have done years ago.