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.
Improving product quality is often a very difficult task for even the best software development organizations. Rajini says the additional benefits of automation include benchmarking, code scanning analysis, end-to-end test cases, and compatibility validation.
DevOps is represented by a set of principles and practices that help improve communication and collaboration between development and operations. Bob Aiello and Leslie Sachs have put together a great introduction showing how quality assurance needs to commence at the very start of a DevOps project.
Alan Crouch addresses the question most commonly raised by those who are new to security testing: "How does security testing fit in my QA process?" Alan explains that security testing shouldn't be limited to the QA process, but instead should be applied throughout the entire software development lifecycle. Read this FAQ column for suggestions on how to improve your chances for success in catching security issues.
Matt Heusser presents ten key factors to establish a team cadence—the time between running tests and getting a product into production. The shorter the cadence, the less time spent in test/fix/retest land, and the more time spent working on new features.
With mobile and small embedded devices extending the reach of modern computing, the predictions are that wearable computing is definitely the next biggest thing. If you want to know more about the wearable device revolution, Mukesh presents facts that will convince you this is the next hottest trend.