Better Software Magazine Articles

Resistance Is Futile

Why do so many people resist change, even when that change will be for the better? It's simple, really. Every change ends something, and endings mean loss. People don't like loss. Even the best changes mean something familiar will end.

Lee Copeland's picture Lee Copeland
Understanding Software Performance Testing Part 1

Most people don't fully understand the complexities and scope of a software performance test. Too often performance testing is assessed in the same manner as functional testing and, as a result, fails miserably. In this four-part series we will examine what it takes to properly plan, analyze, design, and implement a basic performance test. This is not a discussion of advanced performance techniques or analytical methods; these are the basic problems that must be addressed in software performance testing.

Dale Perry's picture Dale Perry
Reloadable Test Data-O-Matic

Reloadable test data takes more time up front (as compared to on-the-fly data creation), but saves blood, sweat, and tears in the long term. It also virtually eliminates "works on my machine" bugs, creates a more intricate and realistic environment, and is the first step on the road to test automation.

Tanya Dumaresq
Off the Trails

A focused approach toward testing a product is important, but sometimes we discover information that we didn't anticipate at all. One of the key skills in testing is dynamically managing our focus; sharpening it sometimes and widening it at other times. If we vary our approaches, we might find something surprising and broaden our coverage.

Michael Bolton's picture Michael Bolton
Lean Portfolio Management: Guiding IT Projects with Business Value

Improving your software development process is only valuable if it fills the highest priority needs for your business clients with speed and quality. Lean principles provide guidance on how to create a structure that lets business priorities drive the selection of the right products for creation and enhancement.

Guy Beaver
Taming the Headless Beast: A Proven Strategy for Testing Web Services

The benefits of Web services are becoming widely demonstrated and accepted. However, these benefits are not without their own challenges. How can you enter data and verify the response of a system without a GUI? Are you ready to tame this headless beast?

David Fern's picture David Fern
Picking the Right Test Automation Strategy for Your Project

The choice of a test automation strategy is a key determining factor in whether your test automation initiative will repay your investment, or become a sink hole devouring time and money. Gerard Meszaros helps you understand what kinds of tests you should be running, which ones should be automated, who should prepare the tests, what tools they should be using, and when the tests should be prepared and run. A well-executed test automation strategy is key to preventing defects rather than finding defects after they have occurred. Gerard gives you the information you need to make an intelligent decision about how to approach test automation to minimize cost and maximize quality.

Gerard Meszaros, ClearStream Consulting
Agile Usability Testing

Agile development has become mainstream in the past few years, and for thousands of companies around the world, it has succeeded in reducing risk and delivering more value for less money. Yet, with the emphasis on pleasing the customer, and the philosophy of doing the simplest thing that could possibly work, there's one area where agile development has fallen short of more traditional methodologies-creating highly usable software. Practices such as test-driven development and continuous integration show little concern for the end-user experience. John De Goes explains the importance of creating humane software, and explains how he has integrated user-interface design and usability testing into the tight feedback loop that is the hallmark of agile development processes.

John De Goes, N-BRAIN, Inc.
Seven Years Later: What the Agile Manifesto Left Out

Although the Agile Manifesto has worked well to help many organizations change the way they build software, the agile movement is now suffering from some backsliding, lots of overselling, and a resulting backlash. Brian Marick believes that is partly because the Agile Manifesto is almost entirely focused outwardly—it talks to the business about how the development team will work with it. What it does not talk about is how the team must work within itself and with the code. Even though those omissions were appropriate then, now more is needed. Teams starting agile need to know that more discipline is required of them, and that discipline is fruitless without a strong emphasis on skills. Teams need to recognize that success is not just fulfilling requirements. It is also increasing productivity and decreasing the consequences of mistakes.

Brian Marick, Exampler Consulting
Risk-based Testing in Action

Risk-based testing allows project teams to focus their limited test efforts on the areas of the product that really matter, based on the likelihood of bugs in those areas and the impact of bugs should they exist. By using risk priority to sequence test cases and allocate test effort, test teams can also increase their chances of finding bugs in priority order and allow for risk-based test triage if necessary.

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.