Software testing/Glossary

< Software testing

Anomaly

In software testing an anomaly is everything that differs from expectation. This expectation can result from a document or also from a persons notion or experiences. Also an anomaly can be a feature or an usability problem, because the testobject may be correct regarding the specification - but it can be improved. Another possibility for an anomaly is that a tester executed the testcase wrong and therefore the expected result is also wrong.
see here for more info.
(see IEEE 1044-1993: Standard Classification for Software Anomalies., page 1, The Institute of Electrical and Electronics Engineers, Inc., New York, USA, 1994, ISBN 1-55937-383-0)

Software

Is more than just source code. There belongs also: programs, procedures and documentation, and data for the concerning processing on a computer system. We (the tutors of this course) count also any testware.
(see IEEE 610-1990: The collection of computer programs, procedures and data, together with possibly associated documentation necessary to understand, install and use it.)

Testware

Including any kind of products, which is helpful for testing. Especially persons from the testing field produce these:
test plans, test cases, test reports, anomaly reports, input files/scripts for test tools, ...
They all should be reusable and therefore managed by configuration management.
This article is issued from Wikiversity - version of the Friday, February 26, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.