GeekArticles

Bug Reporting

Four Keys to Better Test Management

Author: stickyminds.com
Category: Bug Reporting
Comments (0)

There seemed to be a disjoint between development and test groups. There were four things that became very obvious to me, that were necessary to get better organized: 1. To have a common set of ground rules on the test progress, defect reporting, and verification. 2. Be able to convey how is testing going on a frequent basis. 3. Be able to determine what do I need to test and stand behind the reasons why. 4. Maintain good communication with the technical leaders to help move the product through the development phases by being proactive rather than reactive.

Read More...

Read Next: A Look at the Perforce Version Control System

Related Topics

Article :: Package Management in Ubuntu Server

Performance Management

Filio - Distributed File Management

WatinN to automate browser and test sophisticated ASP.NET AJAX sites

Online Task Management Tools

Comments

Subscribe via RSS

Subscribe to GeekArticles.com by Email

Enter your email address:

Subscribe in a reader

Bug Reporting

After the Bug Report

Bug Taxonomies

Bug Movie

Bug Counts vs. Test Coverage

Using Bug-Tracking Systems as Idea Repositories

Bug Reports That Make Sense

Book-The Bug: A Novel

Bug Tracking Basics

Issue Tracking and Project Management with BUGtrack

Defect Management in Development and Test

It’s Not About the Bugs

A paper by Fredericks and Basili

A Closer Look at Estimating the Testing Process

Test Metrics Without Tears

Automation Testing Using Visual Basic 6.0

Equilibrium in Managing Outsourced Testing

Testing Component-Based Software

Test Estimation

A Testing Career in 3-D

Good Status Reporting

Sponsored Links