Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Test the Scenarios (TtS) Process

IP.com Disclosure Number: IPCOM000125490D
Original Publication Date: 2005-Jun-03
Included in the Prior Art Database: 2005-Jun-03
Document File: 5 page(s) / 48K

Publishing Venue

IBM

Abstract

Disclosed is a process for testing systems of software programs that are being created with an iterative development model.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 42% of the total text.

Page 1 of 5

Test the Scenarios (TtS) Process

1.0 Introduction

The Test the Scenarios (TtS) Process supports high-level software verification for projects using an iterative development model. TtS activities are typically referred to as System Verification Test (SVT) in a waterfall development model.

The purpose of TtS is to ensure that the software product under test is ready for customer consumption. This is accomplished by assessing how well the product will meet the intended goals of the software. TtS focuses on the product's behavior in environments reflecting real or anticipated customer environments. TtS verifies many aspects of the customer total experience, such as: installation, migration, performance, scalability, error recovery and others which are part of the customer configuration and operating environment.

2.0 Methodology

Based on information contained in the marketing, content and design documentation, test scenarios are developed to validate software user goals. In addition, other common and/or implicit goals, such as, installability, maintainability, reliability, etc. from CUPRIMDSO and quality requirements are considered in scenario construction. Black-box, user-based scenario test design is employed throughout TtS.

Using a staged delivery plan, scenarios are constructed so that each of the staged deliverables can be tested independently. Each staged deliverable to pass through TtS has its own entry and exit criteria.

The TtS Execution Subprocess conducted during the 'Test the Scenarios' phase is a testing effort focused specifically on scenarios defined for that staged deliverable.

The following areas of testing are required:

Installation/uninstallation


1.


2.

Customer scenarios (as defined in the personas document and other significant customer

scenarios if available).

All areas specified for the final product test phase (see below) are considered based on the specific customer scenario delivery.

As this subprocess may iterate several times during one development cycle, it is essential that as much of the testing be automated as possible.

The TtS Execution Subprocess conducted during the 'Test and Release the Product' phase is primarily a regression testing effort focused on all the scenarios that the product is capable of executing.

The following disciplines and areas of testing are to be considered for inclusion:

Coexistence with other products


1.


2.

Interaction with other products


3.

Performance


4.

Scalability


5.

Installation/Uninstallation


6.

Error recovery and serviceability


7.

Customer scenarios, as defined in the personas document and other significant customer


8.

scenarios, if available.

Migration, if not the first release


9.

Regression


10.

Documentation using the official customer publications

Long Run of at least 5 days to verify memory and database connection leaks, etc.


11.

Configuration testing of many different variations


12.

Platform testing on all supported platforms


13.

Imperative certification


14.

Availabi...