Brooke Bowie explains how "adaptive" software testing provides nimble, high-value software test solutions that bend and shift with the changing needs of the market or the environment. High-value testing does not mean that you need to perform all end-to-end testing or run the full suite of tests; this can potentially create a bottleneck and dampen the velocity. Adaptive tests are always targeted at the most relevant business and quality goals.
It seems like every week the press has yet another story about security breaches or stolen data at some of the world’s largest companies or government agencies. Sometimes the responsibility for ensuring thorough security resides with an IT security group, and other times it gets outsourced altogether. The responsibility seldom falls to testing teams. However, this is changing. Having trained and experienced testers hunt for security bugs will make web applications safer from hackers and will further protect consumers, corporate assets, and brands.. Scott Aziz offers some practical techniques that will help you get started.
The mobile market dynamics are extreme, unpredictable, and fragmented. There are numerous operating systems and a multitude of platform versions, networks, hardware, and form factors making it a challenge to maintain mobile application quality. Find out how to adjust to the shift from traditional to mobile development—which additional elements are a must and which ones can be maintained.
Anyone interested in finding a testing glossary that already exists can use some great online resources. Defined here are several terms in common use that rarely or never make it into the "official" definitions. Finally, there are some terms in use that no longer support the underpinning technology and need to be either retired or expanded.
In the first installment of this article, Dr. James Whittaker discussed turning testing on its head—to revitalize and improve the value of late-stage testing. James also discussed ideas behind empowering your dogfooders, testers, and the crowd to significantly and efficiently improve software quality. In part two, Jason Arbon discusses the research and engineering experimentation behind realizing these ideas into new tools and processes.
Arguments that moving testing forward in the software lifecycle maximizes the return on investment of testing effort have been made and widely accepted. And it is hard to argue with the results. Software is getting better. But what if a shift away from early cycle testing toward late cycle testing could improve quality even more?