Better Software Articles

Please enter an article title, author, or keyword
Writing Effective Bug Reports

Have you ever had a bug returned to you for more information? Have you ever found a critical bug only to have it deferred to another release? Elisabeth Hendrickson tells you how to write effective and informative bug reports that will get noticed.

Elisabeth Hendrickson's picture Elisabeth Hendrickson
Learning Web Performance Testing

Sue Bartlett and Meenakshi Rao highlight some common mistakes to avoid when starting Web performance testing, including trying to select a load-testing tool before evaluating your needs, and trying to outsource performance testing for a complex eBusiness application. They convey two important lessons: First, it's vital that you understand your architecture and your Web site's purpose; second, that kind of understanding is difficult to transfer to a third party.

A Look at Testing Web Applications with eValid

When Robert Sabourin set up a testing lab for a major e-commerce Web-based application, he chose eValid from Software Research, Inc., as the tool for use in functional, performance, and load testing of the application. The product did the job at a very reasonable price, and they were able to find some very important bugs well ahead of their target delivery dates.

Robert Sabourin's picture Robert Sabourin
Checking out of the Burnout Ward

Stefan Jaskiel helps you recognize the signs of job burnout (complacency, difficulty focusing, careless attitude, and helplessness), and offers some strategic interventions.

Stefan Jaskiel's picture Stefan Jaskiel
The Risk in Risk Management

What happens when you perceive a future risk, and others don't? Peter de Jager lays out the hazards of being a risk management visionary.

Peter de Jager's picture Peter de Jager
Agile Development

Technical Editor Brian Marick explains the values behind the Manifesto for Agile Software Development. Above all, Agile practitioners value: individuals and interactions; working software; customer collaboration; and responding to change.

Brian Marick's picture Brian Marick
Reference Point: Measuring and Managing Performance in Organizations

Don Gray recommends Measuring and Managing Performance in Organizations by Robert D. Austin. The book is not a five-step program toward measurement success; instead, it gives an in-depth look at what makes or breaks measurement systems. The book presents information in an intuitive way; if you understand algebra and simple logic, you will understand what Austin is presenting.

Don Gray's picture Don Gray
On the Cost of Quality

Technical Editor Brian Lawrence explains four types of costs of quality: prevention, appraisal, internal failure, and external failure.

Brian Lawrence's picture Brian Lawrence
Know Thy User

Testing, in its broadest sense, means ensuring that your visionaries and programmers are creating a helpful product that people will actually use. As the two authors of this installment of Bug Report illustrate, understanding how those users will operate your application is more than an exercise in empathy; it's a simple key to avoiding some real usability meltdowns.

Brian Marick's picture Brian Marick
Houston, We Have a Problem

Errors start with individuals, and a primary job of testers/QA people is to prevent those errors in the first place. But an equally important part of the job is to find them once they are there, understanding that errors will happen. Jon Hagar asks, "What can we do personally, above and beyond the normal day-to-day jobs that we testers and developers have?"

Jon Hagar's picture Jon Hagar


Upcoming Events

Apr 17
Apr 17
May 01
Jun 05