Method for Categorising Test Scripts from Weights Derived from a Partial Order
Method for Categorising Test Scripts from Weights Derived from a Partial Order
Requirements for systems involving communicating processes (e.g. telecommunication systems) are often described with the aid of graphical notations, such as: Unified Modelling Language (UML), Message Sequence Charts (MSC) or Specification and Description Language (SDL). In using these notations to define requirements engineers tend to think of the most obvious behaviours of the system first (e.g. common system scenarios). However, depending upon the semantics of the graphical notation, specifications may also include non-obvious behaviours that at first glance are not apparent to the engineer when developing the specification. The method described here categorises tests that are automatically generated from a specification according to some suitable numerical weight. The idea is to define a weighting scheme that differentiates the most obvious behaviours from the non-obvious behaviours. In doing so, the user can quickly assess which test scripts represent the obvious behaviours, and consequently can concentrate on making sure that the most obvious behaviours are covered first.
Mitchell, Bill
5d045751-9ef4-4375-9e89-dbae07c90049
Baker, Paul
1685f8ed-e86b-4828-9505-2c22a02c54d6
King, David
fbf9579c-6de4-4169-9184-74134a34c5e2
August 2004
Mitchell, Bill
5d045751-9ef4-4375-9e89-dbae07c90049
Baker, Paul
1685f8ed-e86b-4828-9505-2c22a02c54d6
King, David
fbf9579c-6de4-4169-9184-74134a34c5e2
Mitchell, Bill, Baker, Paul and King, David
(2004)
Method for Categorising Test Scripts from Weights Derived from a Partial Order
Record type:
Monograph
(Project Report)
Abstract
Requirements for systems involving communicating processes (e.g. telecommunication systems) are often described with the aid of graphical notations, such as: Unified Modelling Language (UML), Message Sequence Charts (MSC) or Specification and Description Language (SDL). In using these notations to define requirements engineers tend to think of the most obvious behaviours of the system first (e.g. common system scenarios). However, depending upon the semantics of the graphical notation, specifications may also include non-obvious behaviours that at first glance are not apparent to the engineer when developing the specification. The method described here categorises tests that are automatically generated from a specification according to some suitable numerical weight. The idea is to define a weighting scheme that differentiates the most obvious behaviours from the non-obvious behaviours. In doing so, the user can quickly assess which test scripts represent the obvious behaviours, and consequently can concentrate on making sure that the most obvious behaviours are covered first.
Text
weights_public_version.pdf
- Version of Record
Available under License Other.
More information
Published date: August 2004
Organisations:
Electronics & Computer Science, IT Innovation
Identifiers
Local EPrints ID: 267437
URI: http://eprints.soton.ac.uk/id/eprint/267437
PURE UUID: 4c046516-b4d9-4cda-b0e5-a2de4a9fcd5b
Catalogue record
Date deposited: 01 Jun 2009 10:00
Last modified: 14 Mar 2024 08:50
Export record
Contributors
Author:
Bill Mitchell
Author:
Paul Baker
Author:
David King
Download statistics
Downloads from ePrints over the past year. Other digital versions may also be available to download e.g. from the publisher's website.
View more statistics