The Latest

Four Keys to Better Test Management[article]

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.
Chris DeNardis's picture Chris DeNardis
Software Configuration Management[magazine]

Pat Wegerson recommends software configuration management resources AntiPatterns and Patterns in Software Configuration Management and the online CM Yellow Pages.

Pat  Wegerson's picture Pat Wegerson
How to Make Risk Conversations More Effective[article]

Project managers may be reluctant, even unwilling, to discuss problems that testers discover in a project. In this column, management expert Johanna Rothman gives tips on how best to tell management that "the sky is falling," and how to respond if they don't want to hear about potential problems before they occur.

Johanna Rothman's picture Johanna Rothman
Tinkerable Software[article]

In what ways should software be like a house? In a recent issue of STQE magazine, Technical Editor Brian Marick's musings about the concept of "tinkerable software" generated some interesting discussion about the very nature of software design. This week's column runs a portion of that piece so that our Sticky-minded readers can sink their thoughts into the concept.

Brian Marick's picture Brian Marick
Partners in Testing[article]

Manual software testing can never catch all errors–so can automation help? David Norfolk looks at the pros and cons of automated testing and offers advice–and warnings–on its use.

TechWell Contributor's picture TechWell Contributor
Institutionalizing Poor Quality[article]

Have you ever noticed how many professional activities don't utilize a separate testing phase? Veteran tester and instructor Lee Copeland has. And it got him thinking about our industry and the role a tester plays. In this week's column, you may be surprised by his conclusions.

Lee Copeland's picture Lee Copeland
Managers and the Helpitis Malady[article]

Most of us want to be helpful. It's satisfying knowing that we've been able to solve a problem for another person. But what about those times when the other person doesn't really want our help? In this column, Eileen Strider shows how to offer "healthy" assistance, without giving in to the sickly variety.

Eileen Strider's picture Eileen Strider
A Selection of "Our Take" Columns[article]

"Our Take" is a regular column from the editors at Software Quality Engineering. It appears in the twice-monthly StickyLetter since its inception in September 2000 (originally "STQe-Letter"). From jazz music, to car troubles, to the Lewis and Clark expedition, Robert Rose-Coutré, former StickyMinds.com Editor, will use anything to make a point about building better software. The editors at Software Quality Engineering have compiled a collection of some of these pieces. Musings from StickyLetter's "Our Take" are presented here.

Robert Rose-Coutré's picture Robert Rose-Coutré
Bug Counts vs. Test Coverage[article]

Occasionally, we encounter projects where bug counts simply aren't as high as we expect. Perhaps the product under test is in its second or third release cycle, or maybe the development team invested an inordinate amount of time in unit testing. Whatever the reason, low bug counts can be a cause of concern because they can indicate that pieces of functionality (which potentially contain bugs) are being missed. When low bug counts are encountered, management may begin to wonder about the quality of testing. This article covers techniques for dealing with low bug counts, and methods for reassuring management that coverage is being achieved.

Andrew Lance's picture Andrew Lance
Make Your Point—Without Pointing a Finger[article]

When errors are not detected during testing, somewhere down the line someone has to take responsibility. In this column, Linda Hayes shows you when and how to do so—and you might even be able to turn the situation to your advantage.

Linda Hayes's picture Linda Hayes
Build and Deployment Process for Web Applications[article]

This paper describes practices that have led to a sound and reliable build and deployment process at Hewlett-Packard. Two teams of engineers, later joined by a third, responsible for developing e-service components to build a Web application, chose to use open source development tools/utilities in the "Evolutionary Software Development Lifecycle" environment.

Bhushan Gupta's picture Bhushan Gupta
Measuring Up: How to Preview User Satisfaction before Your Release[article]

Why wait to discover how your users will react to your system when there are ways to measure such things during development? This column describes a simple tool to develop visibility into customer satisfaction. Learn how you can begin to manage expectations so that neither you nor the customer has an unpleasant surprise on release day.

Esther Derby's picture Esther Derby
Giving the Human Touch to Software[article]

Yogita works as a QA/testing professional with Mindfire Solutions, and has written a number of articles on QA and testing strategies. Yogita is currently exploring thoughts of beauty as an area of testing and its relation to usability. Her role at Mindfire has been to implement Quality processes throughout the organization and build a dedicated testing team. The team recently published a White Paper “Porting projects: Test techniques,” downloadable from www.mindfiresolutions.com. Yogita can be reached at yogitas@mindfiresolutions.com.

Yogita Sahoo's picture Yogita Sahoo
Avoiding the Script Cemetery[article]

It's frightening how many companies are on their second, third, or even greater attempt to automate their testing—each time junking months or years of effort and work product. Here, test automation advisor Linda Hayes shows the way to avoid having to bury your automation project.

Linda Hayes's picture Linda Hayes
Wizardry and Requirements[article]

Illusion and reality. Challenges and fear. These are just a few of the elements that go into requirements gathering and management. Being aware of what you know and what you don't know can ensure getting the right requirements. Read on as Harry Potter fan Becky Winant shares some insight and survival tips for requirements analysts.

Becky Winant's picture Becky Winant

Pages

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!