As Williams’ team went through the coding issues discovered by Coverity and fixed the defects, their confidence in achieving their zero-defects goal grew. “We integrated Coverity into our Jenkins CI/CD pipeline,” said Williams. “We ran Coverity on a daily basis, and each night we looked at the snapshot results. Coverity is also integrated with our Jira bug-tracking system. When Coverity identifies a defect, an associated Jira ticket is created to track the progress of its fix.”
“We work under a policy called feature branching; that is, a developer opens a new branch of the code whenever she works on a new feature. We don’t commit to the development branch until the feature branch has gone through Coverity and approved. Only then do we merge it into the development branch, and then ultimately to production.”
Linx’s zero-defect goal, initiated in 2019, was achieved by 2021. As code is changed or new code is introduced, Coverity continues to help Linx identify and fix defect issues. To date, Coverity has analyzed 1.7 million lines of Linx code. In the first year, 97% of the issues identified by Coverity were resolved. Over the course of the next 24 months, Coverity helped Linx maintain a near-flawless risk posture.
“One pleasant surprise is that Coverity has helped our developers code better, as they see the mistakes they’ve made,” Williams said. “From being concerned that Coverity would slow development or flood us with false positives, we think of Coverity as if it were a member of the software team.”
“Another unexpected benefit is that developers aren’t assuming anymore that QA will find the issues for us. Instead, they’re using Coverity to find issues that they can fix before the code reaches QA. Of every 10 issues development has verified as closed, nine have passed QA.”
“The projects I’ve done with Coverity have been very successful,” Williams concluded. “The results have been amazing, and it’s been an incredible journey over the past 36 months. I’m very satisfied with the support I have had, both during installation and maintenance—and not only from the technical staff, but also from customer care. The support team has been very responsive and efficient, resolving 100% of all requests within the stated timeframe.”