Process
Better Software Magazine Articles
Estimates: From Wrong to Real Need a place to go to get the solutions you've been craving? Management Fix is what you've been looking for. In this issue, find out how to create estimates that make sense. |
||
FitNesse: Automated Specification Micah Martin introduces the open source tool FitNesse. |
Micah Martin
March 5, 2004 |
|
The Case of the Crashing Test Site Tom McGreal warns you of problems that may be lurking in your deployment environment. |
Tom McGreal
March 5, 2004 |
|
Practical Career Advancement A word from the Technical Editor |
Brian Marick
March 5, 2004 |
|
Go with the Bug Flow How do you know when your software is done? How do you determine which bugs need to be fixed and which can be tabled for "someday"? Robert Sabourin defines a seven-step process for establishing an effective bug triage system. |
||
Inside the Mind of an Exploratory Tester Among the hardest things to explain is something that everyone already knows. We all know how to listen, how to read, how to think, and how to tell anecdotes about the events in our lives. As adults, we do these things every day. Yet the level possessed by the average person of any of these skills may not be adequate for certain special situations.Exploratory tester James Bach describes eight key skills that expert explorers possess, and how you can develop them too. |
||
Deadlock! Sean Beatty explains what a deadlock is and why testing probably won't catch it. |
Sean M. Beatty
November 19, 2003 |
|
Every Crash, Everywhere You want to know exactly what your users in the field are experiencing. In most cases, they aren’t going to take the time to tell you. Maybe the solution is automated data collection. |
Joel Spolsky
November 19, 2003 |
|
Exhausting Your Test Options In this edition of "Bug Report," Doug Hoffman tells the story of exhaustively testing a 32-bit square root function. |
Doug Hoffman
October 1, 2003 |
|
Orchestrating Integration Testing Verifying the operation of a complex software system can be a daunting task. Here is a systematic approach to the job. This article details six steps for testing duct-taped programs. |
Len DiMaggio
October 1, 2003 |
Pages
Recommended Web Seminars
On Demand | Building Confidence in Your Automation |
On Demand | Leveraging Open Source Tools for DevSecOps |
On Demand | Five Reasons Why Agile Isn't Working |
On Demand | Building a Stellar Team |
On Demand | Agile Transformation Best Practices |