Testing

Articles

The "One Right Way"

For those who believe there has to be one right way to do something, especially in software development - there can be. But that one way isn't likely to come from a single individual. Through collaboration and teamwork, some of the greatest single ideas have evolved.

Lisa Crispin's picture Lisa Crispin
table differentiate analysis results from design results How Early Interface Analysis Reduces Risk

Analyzing a project's interface requirements often starts late and focuses--sometimes exclusively—on creating a snazzy user interface. But failing to conduct interface analysis in a early increases the risk of project delays, overruns, and even failure. In this column, Mary Gorman makes the case for investing in interface analysis by explaining what it is and how it reduces the risk in software projects.

Mary Gorman's picture Mary Gorman
Why You Need to Be Specific about Agile Practice Adoption

Amr Elssamadisy presents one way to share our knowledge that is more specific than full methodologies and processes, more general than war stories, and will help new agile adopters get beyond the mantra "It depends!"

Amr Elssamadisy's picture Amr Elssamadisy
Using Mocks to Verify Interactions

In the March 2006 issue of Better Software magazine, Dan North began a discussion of the evolution of behavior-driven development from test-driven development. Here, North continues the conversation with closer look at "mocks," utility classes that, for testing purposes, pretend to be some component or service with which your object will interact.

Dan North's picture Dan North
So Many Tests, So Little Time

In this corner—A harried project manager whose testing time has just been cut in half. And in this corner—A time-honored management tool to scale back project scope and make testing tasks do-able. Johanna Rothman shows us the ropes of timeboxing and explains why time constraints don't have to be a TKO.

Johanna Rothman's picture Johanna Rothman
Model-Driven Architecture

Powerful new development technologies such as model-based code generation will overwhelm test teams that continue to create tests by hand. It's time for testers to put their own productivity into a higher gear. Harry Robinson tells you all about it in this column.

Harry Robinson's picture Harry Robinson
Testing the Bold and the Beautiful

During testing, testers mostly stress the 'Bold' part of the software and comfortably overlook the 'Beautiful' side. Beauty and functionality are treated as two extreme ends in software quality, where only one of the two can meet perfection at a given time. But the viewers of the famous soap opera The Bold and the Beautiful know very well that both are important. In this article, Yogita Sahoo explains why aesthetics are such an important contribution.

Yogita Sahoo's picture Yogita Sahoo
a timeline for pervasive testing Maximum ROI through Pervasive Testing

Pervasive testing means getting the right people working together through the right processes at the right time for high-ROI testing. Through pervasive testing, all the ideas we've explored so far come together.Web site (as of late-July 2002).

 

Rex Black's picture Rex Black
An informal Quality Risk Analysis for a Hypothetical Word Processor Key Risks to System Quality

Before we can build a high-fidelity test system, we have to understand what quality means to our customers. Test professionals can avail themselves of three powerful techniques for analyzing risks to system quality. Targeting our testing investment by increasing effort for those areas most at risk results in the highest return on investment.

Rex Black's picture Rex Black

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.