Articles

Please enter an article title, author, or keyword
Testing Component-Based Software

Today component engineering is gaining substantial interest in the software engineering community. Although a lot of research effort has been devoted to analysis methods and design strategies of component-based software, few papers address the testing of component-based software. The paper identifies and classifies the testing issues of software components and component-based software according to working experience.

TechWell Contributor's picture TechWell Contributor
Maximizing the Value of Your Test Environmnt

The objective of this paper is to provide insight to the integrated processes, financial and resource requirements, and technical components necessary to achieve a robust end-to-end test environment.

A fully integrated environment will enable end-to-end testing, quality improvement and pre-production certification for your suite of applications. The presentation further examines the vision, components, approach and methodology, and business processes that are critical to a successful test environment.

TechWell Contributor's picture TechWell Contributor
Managing Outsourced Testing (On time and On Budget)

Outsource testing can be a great way to get testing tasks accomplished when short on staff or equipment. Outsourcing can also be a great way to complement an existing QA group. However, it can also be a very costly approach towards testing and may not always be the best solution for a project. This paper will address how to define needs, evaluate labs and ways to merge an outsource effort into an existing staff.

George Hamblen
Cost-Benefit Analysis of Test Automation

The purpose of this paper is to provide some practical guidance for understanding and computing cost and benefits from test automation. It describes some financial, organizational, and test effectiveness impacts observed when software test automation is installed.

TechWell Contributor's picture TechWell Contributor
Is Software Testing Advancing or Stagnating?

The quality movement started in 1924 when Walter Shewhart gave his boss at Bell Labs a memo suggesting the use of statistics to improve quality in telephones. Later came Juran and Deming, and the movement was well on its way. Not surprisingly, the software industry eventually took up the challenge of systematically improving quality. Let's look at how that began.

Steve Whitchurch
Use Case Derived Test Cases

Use Cases are used to specify the required functionality of an Object-Oriented system. Test cases that are derived from use cases take advantage of the existing specification to ensure good functional test coverage of the system.

TechWell Contributor's picture TechWell Contributor
Test Automation for Multi-Platform Client-Server Software

This paper is based on our testing experience of two major releases (version 6 and version 7) of the multi-platform client/server software, SAS/SHARE product which is the database management system for SAS users. It describes our test automation strategy for version 6 and identifies the achievements and weaknesses of our approach and explains how we improve our test process.

The test process improvement effort for version 7 includes reduction of test automation level, use of macros that facilitate reproduction of defects in an interactive manner and extensive use of mega tests for early detection of defects as well as cross host and cross version tests.

Heesun Park
Automated Test Generation

The challenge for testers: reduce the testing interval without reducing quality. One answer: find a new way to approach test design and test generation. This paper will discuss an ongoing Lucent Technologies experiment in automated test generation from a behavioral model of the software product under test. Results indicate that our new approach can increase the effectiveness of our testing while reducing the cost of test design and generation.

TechWell Contributor's picture TechWell Contributor
Mutation Testing: A New Approach to Automatic Error-Detection

Mutation Testing is a powerful method for finding errors in software programs. This paper will describe the process of mutation testing and how a new approach to this technology benefits the software industry.

TechWell Contributor's picture TechWell Contributor
When Should a Test Be Automated?

The question is how to make a rational decision about which tests to automate. When I take a job as a contract tester, I typically design a series of tests for some product feature. For each of them, I need to decide whether that particular test should be automated. This paper describes how I think about the tradeoffs.

Brian Marick

Pages

Upcoming Events

Apr 27
Jun 08
Sep 21