|
From One Expert to Another: Paul Poutanen Paul Poutanen has developed extensive mobile expertise working in management for wireless hardware and cellular location firms such as Wi-LAN and Cell-Loc before launching Mob4Hire. In this interview with Jonathan Kohl, Poutanen discusses the complex global testing process for mobile devices.
|
|
|
STAREAST 2012 Keynote: Testing Trends: Cloud, Virtualization, and Mobility
Video
Almost daily, we see reports of software failures that harm enterprises and impact the brand, putting testing organizations and their efforts in the spotlight. Fortunately, testers are now in one of the most exciting times in the software industry’s history!
|
Theresa Lanowitz, voke, inc.
|
|
The Evolution of Agile: A Conversation with Bob Galen In this interview with online editor Jonathan Vanian, Bob Galen discusses how agile has influenced testing over the years, the role of a tester in an agile project, and what exactly is “session-based exploratory testing.”
|
|
|
How Do You Write Good User Stories? Expert answers to frequently asked questions. In this issue, David Hussman explains how to write good user stories.
|
|
|
Increase Quality with Table-Driven Acceptance Tests Vague or ambiguous requirements can cause loops in development processes. Creating requirements that include acceptance tests cuts down on the looping and increases the flow of working software to the customer.
|
|
|
Writing Good Test Cases We all know writing test cases is an integral part of the testing activity. In order to write good test cases, we must first understand what a test case is and why we need to write test cases. Can’t we live without writing test cases?
|
|
|
Simplify Your Combinatorial Testing Combinatorial testing is effective for testing multiple, non-sequential inputs that affect a common output in complex software. But, it's easy to misapply it or become a slave to the output. Learn to overcome limitations and benefit fully from this technique.
|
|
|
Focusing Test Efforts with System Usage Patterns Faced with the reality of tight deadlines and limited resources, many software delivery teams turn to risk-based test planning to ensure that the most critical components of the software are production ready. Although this strategy can prove effective, it is only as good as your underlying risk analysis. Unfortunately, understanding where risk lies within a product is difficult with the analysis often resulting in little more than an “educated guess.” These risk-based testing exercises can lead to uneven test coverage and the uneasy feeling that the team has neglected to test what is really important. Dan Craig describes how to employ system usage patterns and production defect reports to identify the real risks in a system.
|
Dan Craig, Coveros, Inc.
|
|
Using Test Automation Frameworks As you embark on implementing or improving automation within your testing process, you'll want to avoid the "Just Do It" attitude some have taken. Perhaps you've heard the term "test automation framework" and wondered what it means, what it does for testing, and if you need one. Andrew Pollner, who has developed automated testing frameworks for more than fifteen years, outlines how frameworks have grown up around test automation tools. Regardless of which automation tool you use, the concepts of a framework are similar. Andrew answers many of your questions: Why build a framework? What benefit does it provide? What does it cost to build a framework? What ROI can I expect when using a framework? Explore the different approaches to framework development and identify problems to watch out for to ensure the approach you take will provide years of productivity.
|
Andrew Pollner, ALP International Corp
|
|
Agile Testing: Uncertainty, Risk, and How It All Works Teams that succeed with agile methods reliably deliver releasable software at frequent intervals and at a sustainable pace. At the same time, they can readily adapt to the changing needs and requirements of the business. Unfortunately, not all teams are successful in their attempt to transition to agile and, instead, end up with a "frAgile" process. The difference between an agile and a frAgile process is usually in the degree to which the organization embraces the disciplined engineering practices that support agility. Teams that succeed are often the ones adopting specific practices: acceptance test-driven development, automated regression testing, continuous integration, and more. Why do these practices make such a big difference? Elisabeth Hendrickson details essential agile testing practices and explains how they mitigate common project risks related to uncertainty, ambiguity, assumptions, dependencies, and capacity.
|
Elisabeth Hendrickson, Quality Tree Software, Inc.
|