When can a bug report be considered redundant because it is already reported in the bug management system? If you ask the developers, if two bugs are caused by the same mistake in the code, it’s enough to report one of them. But Michael Stahl has good arguments from a tester's perspective about why it's better to err on the side of over-reporting bugs.
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.
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.
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.
QA is often considered that lonely department of testers whose job is to find defects before the customer does. It's not always glamorous, but QA deserves to be recognized as a key cog in the testing machine. To achieve business goals, it is Susan Bradley's view that the QA process needs to be embraced throughout the entire software development lifecycle.
Finding defects late is a common issue when teams don't consider levels of precision or detail. You must take into account how stories and features fit into the system. In this FAQ column, Janet Gregory tells you how you should remember the big picture—even while testing the small stuff.
In this interview, Sam Kaufman, the founder and CTO of BugReplay, explains why most teams don’t put enough emphasis on bug reporting—even though agile and DevOps have made it even more important than before. He also details where DevOps can improve and where he sees it in five years.
In this interview, Annette Ash, a coach and trainer with SolutionsIQ, talks about the dirty term in the room: quality metrics. She reveals whether tracking metrics is beneficial, what it accomplishes, and what should be tracked with regards to software quality.
In this interview, Neeraj Tripathi, vice president of Global QA at Infor, goes over the principles of effective software quality management. He explains how to measure customer satisfaction and how active QA involvement eliminates defects early and shifts quality left.
In this interview, TechWell speaks with Andreas Grabner, a performance engineer who has been working in this field for the past fifteen years. At STARWEST 2015, he presented DevOps: Find Solutions, Not More Defects.
Measuring software development is difficult. Measuring the return on investment (ROI) of complex initiatives (such as adopting agile) is even more difficult. One department at IBM struggled to reduce a list of 150 metrics down to a top twenty to use in consulting engagements. Through the...
QA and test departments often are composed of employees with business backgrounds who have little training when it comes to software testing. Though they are engaged, these team members can get overwhelmed by the thousands of test cases they have to execute over and over...
You are responsible for addressing quality problems that are plaguing your product and having an adverse impact on the business. Have you been challenged to provide a simple mechanism for quantifying and tracking key performance indicators selected by your organization. The ultimate goal...
In the past two decades agile has become the popular development methodology. Businesses have been rushing to adopt agile processes because it promises to save money and deliver working software more quickly. However, for many businesses, software quality has not improved—and...