Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Software Testing Dictionary

Software Testing Dictionary

Ratings: (0)|Views: 636|Likes:
Published by api-3765353
This contains all the terms in Software testing tools
This contains all the terms in Software testing tools

More info:

Published by: api-3765353 on Oct 16, 2008
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Software Testing Dictionary

A free, searchable by word and topic on-line vocabulary and thesaurus with definitions, synonyms and quotations for over 300 terms associated with Software Testing and QA (Quality assurance)

Acceptance Test. Formal tests (often performed by a customer) to determine whether or

not a system has satisfied predetermined acceptance criteria. These tests are often used to
enable the customer (either internal or external) to determine whether or not to accept a

Accessibility testing. Testing that determines if software will be usable by people with
Ad Hoc Testing. Testing carried out using no recognised test case design technique.
Acronyms and Abbreviations related to software testing This page lists many acronyms
and abbreviations that can be related to software testing
Algorithm verification testing. A software development and test phase focused on the
validation and tuning of key algorithms using an iterative experimentation process.[Scott
Loveland, 2005]
Alpha Testing. Testing of a software product or system conducted at the developer's site
by the customer.
Artistic testing. Also known as Exploratory testing.
Assertion Testing. (NBS) A dynamic analysis technique which inserts assertions about
the relationship between program variables into the program code. The truth of the
assertions is determined as the program executes.
Automated Testing. Software testing which is assisted with software technology that
does not require operator (tester) input, analysis, or evaluation.

(1) An independent examination of a work product or set of work products to assess
compliance with specifications, standards, contractual agreements, or other criteria.

(2) To conduct an independent review and examination of system records and
activities in order to test the adequacy and effectiveness of data security and data integrity
procedures, to ensure compliance with established policy and operational procedures, and
to recommend any necessary changes. (ANSI)

ABEND Abnormal END. A mainframe term for a program crash. It is always associated
with a failure code, known as an ABEND code.[Scott Loveland, 2005]
[Software Testing Dictionary Back to Top]
Background testing. Is the execution of normal functional testing while the SUT is

exercised by a realistic work load. This work load is being processed "in the background"
as far as the functional testing is concerned. [ Load Testing Terminology by Scott
Stirling ]

Bandwidth testing. Testing a site with a variety of link speeds, both fast (internally

connected LAN) and slow (externally, through a proxy or firewall, and over a modem);
sometimes called slow link testing if the organization typically tests with a faster link
internally (in that case, they are doing a specific pass for the slower line speed

only).[Lydia Ash, 2003]
Basis path testing. Identifying tests based on flow and paths of the program or system.
[William E. Lewis, 2000]
Basis test set. A set of test cases derived from the code logic which ensure that 100\%
branch coverage is achieved. [BCS]
Bug: glitch, error, goof, slip, fault, blunder, boner, howler, oversight, botch, delusion,
elision. [B. Beizer, 1990], defect, issue, problem
Beta Testing. Testing conducted at one or more customer sites by the end-user of a
delivered software product or system.
Benchmarks Programs that provide performance comparison for software, hardware,
and systems.
Benchmarking is specific type of performance test with the purpose of determining
performance baselines for comparison. [Load Testing Terminology by Scott Stirling ]
Big-bang testing. Integration testing where no incremental testing takes place prior to all
the system's components being combined to form the system.[BCS]
Black box testing. A testing method where the application under test is viewed as a black

box and the internal behavior of the program is completely ignored. Testing occurs based upon the external specifications. Also known as behavioral testing, since only the external behaviors of the program are evaluated and analyzed.

Blink testing. What you do in blink testing is plunge yourself into an ocean of data-- far
too much data to comprehend. And then you comprehend it. Don't know how to do that?
Yes you do. But you may not realize that you know how.[James Bach's Blog]
Bottom-up Testing. An approach to integration testing where the lowest level
components are tested first, then used to facilitate the testing of higher level components.
The process is repeated until the component at the top of the hierarchy is tested. [BCS]
Boundary Value Analysis (BVA). BVA is different from equivalence partitioning in that

it focuses on "corner cases" or values that are usually out of range as defined by the
specification. This means that if function expects all values in range of negative 100 to
positive 1000, test inputs would include negative 101 and positive 1001. BVA attempts to
derive the value often used as a technique for stress, load or volume testing. This type of
validation is usually performed after positive functional validation has completed
(successfully) using requirements specifications and user documentation.
read tutorial Boundary Value Analysis

Branch Coverage Testing. - Verify each branch has true and false outcomes at least
once. [William E. Lewis, 2000]
Breadth test. - A test suite that exercises the full scope of a system from a top-down
perspective, but does not test any aspect in detail [Dorothy Graham, 1999]
BRS - Business Requirement Specification
[Software Testing Dictionary Back to Top]
Capability Maturity Model (CMM). - A description of the stages through which

software organizations evolve as they define, implement, measure, control and improve
their software processes. The model is a guide for selecting the process improvement
strategies by facilitating the determination of current process capabilities and
identification of the issues most critical to software quality and process improvement.

How is Capability Maturity Model organized?
Capture-replay tools. - Tools that gives testers the ability to move some GUI testing

away from manual execution by \u00ef\u00bf\u00bdcapturing\u00ef\u00bf\u00bd mouse clicks and keyboard strokes into scripts, and then \u00ef\u00bf\u00bdreplaying\u00ef\u00bf\u00bd that script to re-create the same sequence of inputs and responses on subsequent test.[Scott Loveland, 2005]

Activity (7)

You've already reviewed this. Edit your review.
1 hundred reads
akbisoi1 liked this
Satish Marri liked this
sareeee liked this
vishalanandache liked this
DeleProsper liked this
kloutet liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->