|
Hybrid Verification: Mixing Formal Methods and Testing The ability to verify contracts either statically or dynamically, coupled with recent advances in proof technology, has opened up a new and promising approach to verification. Critical code can be proved with formal methods, and less critical code can be verified using traditional testing, with a clear separation at the interfaces between the two.
|
|
|
4 Strategies for a Structured QA Process Being a software tester is no longer just about finding bugs. It is about continuous improvement, defining a clear test strategy, and going that extra mile to improve quality. Following a consistent, structured approach to QA will help you acquire more knowledge about the product you are testing, ask questions you otherwise may not have thought of, and become a true owner of quality.
|
|
|
Exit Criteria, Software Quality, and Gut Feelings Bug counts and trends don't cover all the quality aspects of a product. A good exit criteria list provides an orderly list of attributes that research and experience showed to have impact on product quality, so you can monitor the product quality at any given time and forecast the expected status at release. That's how you improve your product.
|
|
|
7 Test Automation Requirements for Higher Software Quality An advanced, efficient test automation platform, combined with a more systematic and comprehensive architecture, can help boost quality assurance operations to a whole new level. In order to best maximize a software product’s reliability, consider these seven requirements for your test automation efforts.
|
|
|
The Collaboration of Unit Testing Unit testing can be one of those polarizing topics in software development. But Joe DeMeyer says good unit testing allows you to explore products deeper, lowers your estimate, improves quality, and maintains productivity pace. Here, he talks about how you can get your developers and business team on board.
|
|
|
Clean Up Your Bug Tracker and Keep Numbers Manageable A good team likely is trained to consistently report defects as accurately and promptly as possible. This means that over time the bug backlog builds up, and looking for what bugs to fix starts to seem like searching for a needle in a haystack. The best way to keep your tracker under control is to improve the quality curve earlier.
|
|
|
Being the Devil’s Advocate for Software Quality What if someone were to say that most of the time, quality does not matter? That you should only aim for the minimal amount of investment in testing to get the product out the door to start making money? Here, Rob Cross takes the “devil’s advocate” position and provides some arguments against striving for quality. How would you refute them?
|
|
|
8 Simple Ways to Improve Distributed QA Teams Geographically distributed QA teams and the challenges that they face are a common and ongoing topic in the software development world. In this article, Kevin Wilson focuses attention on eight simple solutions that can help maximize the effectiveness of your distributed QA team.
|
|
|
Accelerating the Adoption of Technical Practices Agile teams are supposed to take responsibility for how they work and how they learn. But what if you need to jump-start that learning? Agile transformation is about making this happen rather than waiting for it to happen. You need to get your team to learn the technical side of agile, and soon. Here are some effective approaches.
|
|
|
I Go Back: Valuable Lessons in Quality Engineering Terry Wiegmann noticed that in certain conversations with clients and team members, a single phrase can take her back to some “aha” moments when she grasped fundamental quality concepts. She shares some of these major learning moments throughout her career and how they can apply to quality engineering.
|
|