Testing

Better Software Magazine Articles

Testing the Contract Metaphor

A contract represents a service agreement between two parties, the bounded provision of service by one party to the other. This metaphor also applies to how we can think about the relationship between unit tests and code. A contractual mindset encourages test names and partitioning based on clear propositions, backed up with executable examples.

Kevlin Henney's picture Kevlin Henney
Crash Course in Proficient Presenting

Ben has to make a presentation at the next all-hands meeting. It'll be his very first presentation, and just thinking about it has sent him into a panic. Fortunately, he has the support of an experienced speaker and coach who offers advice and encouragement to help him become a proficient, panic-free presenter.

Naomi Karten's picture Naomi Karten
Issues about Metrics about Bugs

Managers often use metrics to help make decisions about the state of the product or the quality of the work done by the test group. Yet, measurements derived from bug counts can be highly misleading because a "bug" isn't a tangible, countable thing; it's a label for some aspect of some relationship between some person and some product, and it's influenced by when and how we count ... and who is doing the counting.

Michael Bolton's picture Michael Bolton
GUT Instinct

Whether or not a unit test is considered good is not simply about what it tests: It is also very much about "how" it tests. Is the test readable and maintainable? Does it define the expected behavior or merely assume it? To be sustainable, the style of a unit test is just as important as the style of any other code. Perhaps a little surprisingly, the most commonly favored test partitioning style does not meet these expectations.

Kevlin Henney's picture Kevlin Henney
What to Expect When You're Automating Testing

After learning the basics of testing frameworks, writing tests for your existing codebase can be a daunting challenge. Where should you start testing, and what kind of tests will be the most effective? Learn how to kick-start your testing and some solutions to problems teams frequently encounter.

Daniel Wellman's picture Daniel Wellman
Virtual Realities: Best Practices and Common Pitfalls of Adopting Virtual Lab Automation

Virtual Lab Automation (VLA) is a ground-breaking technology that promises quantifiable benefits for application development and test organizations, including faster lab deployment, less manual setup work, greater resource flexibility and utilization, and easier reproduction of defects. In this article, Skytap's Ian Knox discusses the best practices and common pitfalls associated with adopting a VLA solution. In addition, he outlines the steps to evaluate a virtualization solution for your test organization and provides further resources to help you get started.

Ian Knox's picture Ian Knox
The Trouble with Derivation

This article discusses the dark underbelly of derivation: the fragile base class. It's possible to modify a base class in such a way that, even though you've improved its implementation and all your tests work just fine, you've nonetheless damaged the derived classes, perhaps fatally.

Allen I. Holub's picture Allen I. Holub
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's picture Tanya Dumaresq

Pages

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!