Testing Resources & References
Some Testing Definitions
Test Engineering – A systematic approach and methodology for developing,
implementing, and executing product tests. Test Engineering can include
methods, processes, tools, and techniques that aid the testing definition,
evaluation, execution, and reporting activities.
Pragmatic Systems Testing™ – A testing methodology that flows from Product
Requirements to a Test Plan to Test Procedures to Test Cases using test
coverage matrices and risk assessments to focus and effectively utilize limited
test resources.
White Box Tests – Type of testing that allows the test engineer to access and
manipulate parameters, attributes, flow, or data within a function or class that
is not normally accessible to an end user.
Black Box Tests – Type of testing that concentrates on user interfaces and data,
and treats underlying code as a defined process or transformation associated
with a stimulus and a response.
Unit Tests – Low level testing that focuses on individual functions, modules, or
classes. Typically, this is the responsibility of the developer in most development
methodologies.
String Tests – Testing that builds on lower level tests to ensure that interfaces,
data structures, and messages interact correctly across a set of functions or
scenarios.
End-to-end Tests – Testing to ensure that data flows across the system and
infrastructure as specified and expected.
Systems Tests – Testing associated with normal and extended operation of the
product under varying conditions and environments. This also includes reliability,
compatibility, scalability, and interoperability testing.
User Acceptance Tests (UAT) – Testing that focuses on user scenarios associated with
the operation and use of the product by customers/users. Also, includes
installation testing.
Functional Testing – Type of testing intended to ensure that a product conforms to
stated product functions, capabilities, quality, and/or requirements.
Regression Testing – Type of testing intended to ensure that unchanged areas of code
do not experience unintended side effects, timing issues, or performance changes
due to changes elsewhere in the product or changes introduced inadvertently.
Performance Testing – Type of testing intended to measure/baseline responses of a
system or subsystem to a set of stimuli. Responses are compared to specific
targets or requirements, or relative to a previous standard, expectation, or
measurement. Typically used in conjunction with Load testing.
Load Testing – Type of testing to determine system responses to varying usage of
the system over an extended period of time. Attempts to simulate operational
usage of the product with a large number of users, clients, or consumers of
resources.
Stress Testing – Type of testing to determine system response to maximum loads
and consumption of resources. Typically to uncover bottlenecks, timing issues,
worse-case results, recoverability, robustness, and failure modes.
Some Online Test Resources
©2007 Round Rock Systems Test, Inc.
