Articles

Please enter an article title, author, or keyword
A Tester’s Tips for Dealing with Developers

Is the tester doing a good job or a bad job when she proves that the program is full of bugs? It’s a bad job from some developers’ points of view. Ridiculous as it seems, there are project managers blaming testers for the late shipment of a product and developers complaining (often jokingly) that “the testers are too tough on the program.” Obviously, there is more to successful testing than bug counts. Here are some tips about how testers can build successful relationships with developers.

Yogita Sahoo's picture Yogita Sahoo
e-Talk Radio: Pettichord, Bret, 8 February 2001

Ms. Dekkers and Mr. Pettichord talk about why testers and developers think differently, and why they should think differently.

Bret Pettichord's picture Bret Pettichord
Making Sure You Buy the Right Packaged-Software Solution

The slick brochure promises every feature you can imagine, and the sales rep assures you that his package will do just what your users want. But that's what the other vendor's sales rep said, too. Sound familiar? Karl Wiegers recommends several requirements development practices that can help you select the right commercial package solution. Key practices include identifying user classes, defining their use cases, creating test cases from the high-priority use cases, documenting pertinent business rules, and exploring the users' performance goals and other quality attributes.

Karl E. Wiegers
e-Talk Radio: Derby, Esther, 4 January 2001

Ms. Dekkers and Ms. Derby talk about various management issues (e.g., promotions based on technical skills instead of people management skills, and the importance of interpersonal skills training for managers) and modeling organizational change.

Esther Derby's picture Esther Derby
A Problematic Truth

"No Fred, we're not considering you for that promotion. You're too valuable where you are." How many of us have heard those words, or said them at least once to our staff? Sometimes, we use the "too valuable" phrase to avoid discussing problems with a staff member, problems you can bring out in the open and manage.

Johanna Rothman's picture Johanna Rothman
What Is Exploratory Testing?

Exploratory software testing is a powerful and fun approach to testing. In some situations, it can be orders of magnitude more productive than scripted testing. I haven't found a tester yet who didn't, at least unconsciously, perform exploratory testing at one time or another. Yet few of us study this approach, and it doesn't get much respect in our field. It's high time we stop the denial, and publicly recognize the exploratory approach for what it is: scientific thinking in real time. Friends, that's a good thing.

James Bach's picture James Bach
From a team to A-Team

The challenge was to introduce agility (Scrum) across the AOL Publishing organization. If we subtract the editorial staff, the agile transformation affected roughly 3,000 employees one way or the other. The agile consultant and coach tried to tackle several issues under one “reward and recognition program” umbrella. For example, “How do we know that the 50-70 project teams, who were working in parallel at any given moment, were really doing agile?”

TechWell Contributor's picture TechWell Contributor
When the Going Gets Tough, the Tough Get...Gentle?

Software projects are filled with productivity needs and deadline pressures. As a project manager, you may feel responsible for project deliverables yet highly dependent on others to complete their work. It's common to push, prod, and heavy-handedly coerce your team to go faster. Sometimes this has the desired effect. And even if it doesn't, you can at least claim you pushed as hard as you could. But is that really all that can be done? Eileen Strider suggests another tool at your disposal.

Eileen Strider
It Depends

Many of us would like a precise answer to the question: "What's the correct staffing ratio for developers to testers in my product organization?" Usually, though, the only answer is "It depends." Your answer depends on your situation: the kind of project you're working on,
your schedule constraints, the culture you work in, and the quality expectations for the product. This paper discusses the thought process involved in deciding on your correct staffing ratios.

Johanna Rothman's picture Johanna Rothman
System Testing Strategies for Highly Available Clustered Systems

This paper focuses on the strategies and challenges of testing real-world, large and complex, highly available clustered systems in the following areas: Test planning, Strategies and methodologies; Defect tracking processes; System Configuration tests; Cluster and storage fault injection tests; Effective testing practices.

The information provided in this paper is aimed at helping test engineers understand many of the quality assurance issues involved in testing large and complex systems.

Subbarao Jagannatha

Pages

Upcoming Events

Apr 26
Jun 07
Oct 03
Nov 14