Skip to main content
If Everyone Wrote Clean Code Would You Too?
As I mentioned earlier, Coverity is one of the vendors to watch. They really can make your code cleaner, more reliable, and more secure.

I saw a presentation given by Coverity CTO, Ben Chelf , that unequivocally proved to a room full of highly skilled developers that it is neither simple or pleasant to cover 100% of your code when searching for bugs and the simplest of things are not really as simple as they appear. At the end of the session, developers were clamoring to find out more about what Coverity could do for them. This is what every good demo sets out to accomplish.

Coverity views the software life cycle as “design / code / system test / QA / release. " The Coverity products fit squarely in the “code and system test” portion of the life cycle and focus on quality, security, and concurrency. By conducting 100% code coverage of all possible paths in the source code, Coverity can uncover bugs early in the life cycle – read as - before deployment of the code. This basic truth about detecting bugs earlier in the life cycle has been around for quite some time, yet many development organizations choose to not invest in this practice? Why?

The area of application security is another gold mine for Coverity. Coverity knows that the same security issues that exist in enterprise software applications will make appearances in device software. There is a remarkable bridge here with what Coverity can deliver in terms of application security. Yes, network security is important, but application security represents the last mile and the most opportunity for any would be hackers. One of the largest objections to application security tools has been the high rate of false positives. Coverity promises the false positive rate to be less than 20%. Security vulnerabilities are coming to a device or an application near you, so be prepared.

And, finally, Coverity can handle concurrency issues by detecting errors in multi-threaded programs.

Coverity has a stable of innovative products to help developers eliminate costly bugs and security vulnerabilities. And, Coverity understands that source code is source code regardless of where and what it may be powering. Software bugs show no favoritism and will appear in enterprise software or device software – it is up to the wise developer to eliminate them early and easily.

What’s next?...we live in a global world, shouldn’t your products and applications?
t

Popular posts from this blog

Release Management - We Want YOUR Opinion

Releasing software, the last step to getting your software creation to your customers! Every team releases software differently, but everyone wants the release to be a success. So, regardless of how you release, how frequently you release, or how much you know about what you are releasing – we want your opinion! voke , the analyst firm focused on the edge of innovation, is conducting research on the topic of release management. We are looking for people exactly like you to share your opinion on software release management.  Please help out by letting us know what you think. The survey will take about 10 minutes to complete. Click here to share your story on release management. t

API Testing – Stop Waiting and Start Testing ASAP!

We have all heard that testers must keep pace with developers to deliver software faster. However, most testers continue to test at the UI level – which is constantly changing, so testers have to wait, and that impacts the ability to meet business demands for faster software releases. It becomes a cycle that testers have a hard time escaping. Testers want to be able to test earlier, reduce risk, and identify defects sooner – all to satisfy the customer. API testing is the perfect way to supplement traditional UI testing, keep pace with development, and deliver better quality at scale!  API testing can help you test earlier, faster, and more efficiently! And now, we have the data to show you the benefits of API testing including how much time is spent on UI testing alone, how much (or should I say little) time is spend on unit and API testing, and how much coverage is achieved.  We will be premiering the results of our recent survey on API testing in a webinar with Paraso

World Quality Report 2016 – 2017 Launch Highlights

I had the opportunity to attend the launch of the 8 th annual World Quality Report 2016 -2017 (WQR) authored by Capgemini and Sogeti , in collaboration with HPE . You can download a complimentary copy of the WQR here  This annual undertaking by the three companies is a global survey of 1600 participants consisting of 44 questions. The result is an 80-page report that provides a baseline for testing and QA trends. The launch event featured WQR co-authors Mark Buenen, Vice President, Global Leader, Sogeti QA and Testing Practice, Netherlands and Govindarajan Muthukrishnan, Senior Vice President,   Financial Services Testing Leader, United Kingdom. The co-authors spoke eloquently for about 30 minutes each on highlights of the WQR.  Following are some of the highlights from Mark and Govind’s WQR launch presentation. Overview As organizations continue on the path of digital transformation, there is immense pressure on the QA organization to deliver custome