Please enter an article title, author, or keyword
How Many Testers Is Enough?

This article takes a seemingly simplistic view at managing resources and projects.

Robert Rivera
Adventures in Session-Based Testing

This paper describes the way that a UK company controlled and improved ad-hoc testing, and was able to use the knowledge gained as a basis for ongoing, sustained product improvement. It details the session-based methods initially proposed, and notes problems, solutions, and improvements found in their implementation. It also covers the ways that the improved test results helped put the case for change throughout development, and ways in which the team has since built on the initial processes to arrive at a better testing overall.

James Lyndsay
Modeling Practice and Requirements

Models are useful in different settings in different ways. Models can test facts, ideas and understanding, simulate operation, and aid coordination between systems and people. In this column, Becky Winant lists six model patterns she has seen in practice in software development organizations, talking about where each is appropriate, and the strengths and weaknesses of each.

Becky Winant
Positioning of Test Automation Services in an Organization

This paper focuses on establishing test automation as a service in the software development organization at the outset, with the importance being given especially to the testing group. Test automation should direct its efforts to increase the efficiency and effectiveness of the manual testing process by providing 'Quality' Test Automation services. Test Automation should always aim at supplementing the manual testing to quickly assess the quality of the application under test through the execution of quality test automation suites. The building blocks of test automation services are discussed thoroughly to successfully finish test automation projects.

TechWell Contributor's picture TechWell Contributor
White Paper: Step Towards Software Excellence: SCM

This article develops a Software Configuration Management (SCM) Reference Model. This model is intended to be a concise and practical guide which brings together in an outline fashion the framework and methodology necessary for planning, customizing, and implementing an SCM approach, independent of specific SCM tool technologies or system platforms.

TechWell Contributor's picture TechWell Contributor
White Paper: Just Enough SCM

This paper explores the relationship between SCM and the modern development models, provides an explanation of how to provide SCM in a quick, concise way, and describes how to adapt the "Just Enough SCM" philosophy to the most demanding standard.

TechWell Contributor's picture TechWell Contributor
 metrics used to estimate a testing project The Test Estimation Process

Estimation is not an easy task. Estimating testing projects is harder. If there are no tools or methodology to support it, the estimation process is a nightmare for those responsible for it. This essay describes a real experience in the estimation process. It also shows some rules, metrics, tools, and tips that guide a testing team through the estimation process.

TechWell Contributor's picture TechWell Contributor
Real World Capacity Assessment

Capacity assessment has become a necessity in today's complex network environments. Indeed, conducting rigorous assessments can not only bring peace of mind and improved performance and stability to the final system, but also saves time and money. Conducting these assessments requires tools that properly address the realities found in environments such as the Internet or enterprise network infrastructures. In fact, conducting assessments without these realistic factors can be risky, often not resulting in a real world picture of the performance or capacity of the system. We introduce CawUsers as the definition of a real world user-assessments using CawUsers will vastly improve the understanding and confidence in a system to meet the demands and rigors found in the real world.

Philip Joung
Manage the Risks and the Process

Including a testing/QA component early in a software project necessarily prolongs the schedule, right? Not so, according to Ross Collard. In this, the third of a three-part series, Collard explains how to anticipate risks and to aggressively manage the process to prevent disaster.

Ross Collard's picture Ross Collard
Can You Predict Danger?

Testers are in a position to see danger coming. Speaking up early about risks that others may not see can save a project. In this article Yogita Sahoo looks at the problem of NOT speaking up, and discusses the unique position of the test team in preventing failures.

Yogita Sahoo's picture Yogita Sahoo


Upcoming Events

Oct 02
Nov 06
Apr 30
Jun 04