Test Planning
Articles
Efficiency and Effectiveness Measures To Help Guide the Business of Software Testing The measurements described in this paper answer the question of whether Software Testing is "doing the right thing" (effectiveness). Once there is assurance and quantification of correct testing, metrics should be developed that determine whether or not Software Testing "does the thing right" (efficiency). |
John Huber
August 22, 2003 |
|
When Should You Start Project Overtime? Many managers believe that overtime, even extended overtime is a good thing, and will help a project make progress. However, most technical people who try to work more than two weeks of overtime make huge numbers of mistakes. Often, they don't realize the mistakes and have already wasted a lot of time and money. |
||
The Sarbanes Effect on Software Development One of the most pervasive, and often justified complaints coming from QA professionals is that senior corporate management seems unaware of their existence, let alone their value. All too often perceived as a necessary evil or discretionary expense, QA is often a target of budget and schedule cuts. But all that could change with the Sarbanes-Oxley Act. In this column, Linda Hayes explains what this new legislation could mean for your QA team. |
||
Maintenance and Support of Test Tools During the lifetime of a test tool it will be necessary to upgrade, maintain, or customize the test tool. The upgrade and maintenance of test tools needs to be carefully managed and planned in order to mitigate the risk of affecting the end users. This article offers a framework for helping organizations cope with the changes that a test tool experiences during its lifetime. |
Jose Fajardo
July 10, 2003 |
|
Test-Physicians, Source Code, and BSODs This is part 3 of a three-part list of nine "commandments" that can be used as a guide to improving your life as a test engineer. These are intended to be useful suggestions as well as for fun. Read on and see what you think. |
||
Oracles, Failures, Models, and Sins This is part 2 of a three-part list of nine "commandments" that can be used as a guide to improving your life as a test engineer. As a response to numerous inquiries about these tenets listed on James' Web site, this column provides his explanations behind the "Thou Shalts." These are intended to be useful suggestions as well as for fun. Read on and see what you think. |
||
Improve Tester Performance Before a software application is released, its upgrade is already being developed. But what about upgrades for software testers? In this column, Johanna Rothman offers some ways to strengthen the existing talents within your test team. |
||
Random Testing and "App Compat" Thoughts of testing tasks keeping you up at night? Looking for some helpful tips? Well then, you've come to the right place. James Whittaker's Software Testing Ten Commandments may be just what the doctor ordered. Curious? Take a peek at this week's column to find out more! |
||
Ten Ways to Guarantee Project Failure Naomi Karten specializes in helping companies succeed in their projects. In this column, however, she gives tongue-in-cheek advice on how to make a project fail. Read on to see if these steps to failure are part of your organization's modus operandi. |
||
Tell the Right Story When preparing for a testing news meeting, sometimes it's hard to fill your report with the latest accurate information. It's sometimes also hard to prioritize elements in your presentation. Finding a happy medium between delivering accuracy and up-to-the-minute details, and prioritizing your presentation, can be a tough balancing act. To be successful you'll need to be well informed about the most important issues and in touch with the needs of your audience. |