While the sporting world may be preparing for a certain college basketball tournament, we’re preparing for a bout of month-long madness of our own.
Next month, we’re kicking of March Mayhem: four weeks of all the crucial software testing information you can handle, culminating in a showdown between the top development testing strategy versus the top QA activity.
Before we can fill out our March Mayhem bracket, we need to narrow down the tournament to the Great Eight activities. Visit our survey page to vote for your top software quality strategy—the one that you and your team could not live without.
Your Guide to the Championship Contenders for "Top Software Development Testing and QA Strategies"
Not sure which practice you want to champion? This guide provides a brief overview:
Development Testing Conference
Static analysis: Compare your code to known best practices. Static analysis tools report a violation when your code deviates from safe, secure, and reliable constructions. This helps you expose defects and help prevent future defects with minimal disruption.
Unit testing: Verify that the code does what it’s supposed to do. Tests can be saved and reused as part of a regression test suite. Some level of test maintenance is required.
Coverage analysis: This technique tells you how much of your code is actually tested when you run your test suite. Coverage analysis is a requirement for safety-critical applications, but has value way beyond cars, insulin pumps, and airplanes.