The Latest

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

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.

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?"

STORM is a software-driven combination of hardware and software that recreates multiple, real-life, WAN links in terms of bandwidth limitations, packet loss, latency, jitter, and more–all in a local area network (LAN) lab. By providing a test bed that brings the WAN into a controlled and repeatable LAN environment, we can test and evaluate the performance and robustness of IP applications or devices before wide-scale deployment, or compare new technologies before field testing.

Do you shudder at the thought of having to learn social etiquette in order to manage your professional network? Networking rituals do have to evolve to fit with new communication mechanisms. But the workings of the human psyche haven't changed, and you still need to learn the skills that are necessary to develop a network that can bolster your career.

Numbers count—no two ways about it. But any numbers you include in a bug report should also include the appropriate units of measure. In an example from their experience, David Wilson and Leonidas Hepis explain the importance of using consistent terminology and units of measure.

Technical Editor Brian Marick uses a fairy tale format to warn software professionals against using easy-to-acquire numbers in place of human judgment.