What Are Your Metrics Trying to Tell You? What Are Your Metrics Trying to Tell You?

Joanne Perold writes that you cannot just look at the numbers; the context behind the data is often far more valuable. Metrics can tell a compelling story or provide meaningful information to anyone who wants to pay attention, but when the focus is only on the number, it can be a disaster.

Joanne Perold's picture Joanne Perold
 Four Solutions Compared How to Test Your Website on Multiple Browsers: Four Solutions Compared

Robbie Bridgewater writes on the difficulty in finding bugs during testing since no single computer can run all of the major browsers—not to mention the added challenge of testing various mobile operating systems. In this article, Robbie compares four possible solutions to this dilemma.

Erle Bridgewater's picture Erle Bridgewater
What to Review If You Can’t Review Everything

Payson Hall shares with us a useful list of review criteria via a case study of a troubled software development project. Reviews can be messy. Sometimes it’s hard to know where to start, particularly when you are in triage mode and can only review a small sample.

Payson Hall's picture Payson Hall
Writing Test Rules to Verify Stakeholder Requirements

Some organizations employ business analysts who are very good at specifying requirements at the beginning of a software project. The advantage of this step is the reduction in ambiguity for the developer and tester of what should be delivered.

Brendan Quinn's picture Brendan Quinn
Test Documenting Over the Cliff

Unless you're in a test role where full, complete documentation is necessary in order to be federally compliant or to keep people from dying or losing a limb, attempting to document every little thing is a fool's errand. Software changes. A lot. With constant change, what we document one day may be obsolete the next.

Bonnie Bailey's picture Bonnie Bailey
As Testers, How Do We Know What We Know?

Software testing is a process of acquiring knowledge about software. But, how do we know what we know or how to acquire knowledge? Rick Scott shows what the study of epistemology means for testers.

Rick Scott's picture Rick Scott
Help Technical Support Help Themselves

This article discusses how testing teams can improve their test coverage and better communicate with technical support to uncover issues earlier than during product implementation. This kind of collaborative work can stop most defects from getting into production.

Ipsita Chatterjee
Manual vs. Automated Code Review

It's a battle between human and machine-a theme that could be ripped straight from a science-fiction story, but it is not. This is a reality many testers face when trying to determine if human expertise and intuition can detect more security flaws than automated tests. In this week's column, security expert Bryan Sullivan weighs both sides and offers his verdict.

Bryan Sullivan's picture Bryan Sullivan
Making Sense of Root Cause Analysis

Applying Root Cause Analysis (RCA) to software problems is fundamentally different from applying it to other engineering disciplines. Rather than analyzing a single major failure, we are usually analyzing a large number of failures with software. In this column, Ed Weller explains how to use RCA to your advantage.

Ed Weller's picture Ed Weller
Lightweight Code Reviews: Team Building for the Rest of Us

The author explores the people side of peer code reviews. Besides the technical and quality benefits, peer code reviews help build better teams. Believe it!

Jason Cohen


StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.