 |
SQAtester com |
| |
|
your software
testing reference on line
|
|
|
|
|
|
Test-Reviews
|
| |
|
| A | B - C |
D - E | F - G | H - I | J
- k - l - m - n - O | P | Q | R
| S | T - u - v - w - x - y - Z |
A
| Automation |
The process of writing a set of instructions that are
designed, scripted, tested, and checked in by a person, then executed by a machine, to produce results that can
be analyzed. |
| Acceptance Testing |
Is the process of comparing a program to its requirements |
| Ad - Hoc testing |
Appropriate and very often syndicated when tester wants
to become familiar with the product, or in the environment when technical/testing materials are not 100% completed.
It is also largely based on general software product functionality/testing understanding and the normal 'Human
Common Sense'. |
| Automation |
The process of writing a set of instructions that are
designed, scripted, tested, and checked in by a person, then executed by a machine, to produce results that can
be analyzed. |
B - C
| Build Acceptance Test |
The build acceptance test is a simplistic check of a
product's functionality in order to determine if the product is capable of being tested to a greater extent. Every
new build should undergo a build acceptance test to determine if further testing can be executed. Examples of a
build acceptance:
Product can be installed
with no crashes or errors that terminate the installation. (Development needs to install the software from the
same source accessed by
QA (e.g. Drop Zone, CD-ROM, Electronic Software Distribution archives, etc.).
Clients can connect to associated
servers.
Simple client server communication
can be achieved |
| Bottom - up |
Start testing with the bottom of the program. The bottom
- up strategy does not exist until the last module is added. |
| client |
The client part of a client-server architecture. Typically,
a client is an application that runs on a personal computer or workstation and relies on a server to perform some
operations. |
| Client-Server |
Testing Systems that operate in client/server environments. |
| Compatibility Test |
This test is used to test compatibility between different
client/server version combinations as well as other supported products. |
| Confidence Test |
The confidence test ensures a product functions as expected
by ensuring platform specific bugs are not introduced and functionality has not regressed from drop to drop. A
typical confidence test is designed to touch all major areas of a product's functionality. These tests are run
regularly once the Functional Freeze milestone is reached throughout the remaining development cycle. |
| Configuration Tests |
These tests are run for product testing across various
system configuration combinations. Examples of configurations:
Cross platform (e.g. Windows Clients against a UNIX server).
Client/server network configurations. Operating systems and database combinations (also including version combinations).
Web servers and web browsers (for web products). The system configurations to test are determined from the product's
compatibility matrix. This test is sometimes called a 'Platform test'.
CET (Customer Experience Test)
An in-house test is performed before the Alpha, Beta, and FCS milestones which is used to determine whether the
product can be installed and used without any problems, assistance, or support from others. |
D - E
| Debug |
An attempt to determine the cause of the symptoms of
malfunctions detected by testing or by frenzied user complaints. |
| Event-Driven |
Testing event-driven processes, such as unpredictable
sequences of interrupts from input devices or sensors, or sequences of mouse clicks in a GUI environment. |
F - G
| Final Installation Test |
Verification that the final media, prior to hand off
to Operations for duplication, contains the correct code which was previously tested and is installable on all
the supported platforms and databases. The product demo is executed and product Release Notes verified. |
| Functionality Test |
This is designed to test the full functionality, features,
and user interfaces of software based upon the functional specifications. |
| Graphical User Interface (GUI) |
Testing the front-end user interfaces to applications
which use GUI support systems and standard such as MS Windows or Motif. |
| GUI Roadmaps |
Step by step walk through of a tool or application, exercising
each screen or window's menus, toolbar and dialog boxes to verify the execution and correctness of the Graphical
User Interface. Typically, this is handled by automated scripts and rarely is used as a manual tests due to the
low numbers of bugs found from them. |
H - I
| Internationalization |
The process whereby software, which was ordinarily designed
to operate within a single language or locale, is enhanced with capabilities and features which allow general support
of a broad range of languages or locales. This usually implies the implementation of internal functions which would
have been required to implement all of the locales within the range of locales, without committing to a particular
one, as well as providing a mechanism for easily "plugging in" strings of the different languages. Use
of the "globalized" software for a specific locale will then require relatively simple "localization"
work. |
J - k - l - m - n - O
| Module testing |
To test large program its necessary to use module testing.
Module testing (or unit testing) is a process of testing individual subprograms (small blocks), rather than testing
the program as a whole. Module testing eases the task of debugging. When error is found, it is known is which particular
module it is. |
| Object |
A defined Windows control, such as a window, dialog box,
check box, label, grid, radio button, or command button. Applications may also contain custom objects that conform
to Windows object programming standards. |
| Object-Ooriented |
Testing systems designed or coded using an object-oriented
approach or development environment, such as C++ or Smalltalk. |
P
| Parallel Testing |
Testing by processing the same (or at least closely comparable)
test workload against both the existing and new versions of a product, then comparing results. |
| Performance |
Measurement and prediction of performance (e.g. Response
time and/or throughput) for a given benchmark workload.
Phased Approach
A testing strategy where test cases are developed in stages so a minimally acceptable level of testing can be completed
at any time. As new features are coded and frozen, they receive priorities for a given amount of time-so that a
concentrated effort is directed toward testing those new features before the effort returns to validate the preexisting
functionality. When no new features are available, preexisting features will be targeted-with priorities set by
Project Leads.
1st level - Minimal Acceptance Test
2nd level - Confidence Tests
3rd level - Full Functionality Test
4th level - Error, Negative, and other Tests
5th level - System level tests |
Q
| QA |
A.K.A. Quality Assurance. Also known as Software Test.
This is the group that performs methodical testing of the products developed by engineering. They make no statement
of the quality of the product and no guaranty of finding all the bugs in a product. Their job is to take an independent
approach to evaluating the product and open bugs against anything they think is broken or not performing as a reasonable
end user might expect. |
| Quality |
The totality of features and characteristics of a product
or service that bear on its ability to satisfy stated or implied needs. Not to be mistaken for "degree of
excellence" or "fitness for use" which meet only part of the definition. |
R
| Regression Tests |
These tests are used for comprehensive re-testing of
software to validate that all functionality and features of previous builds (or releases) have maintained integrity
of features and functions tested previously. This suite of tests includes the Full Functionality Tests and bug
Regression Tests (automated and manual). |
S
| Sanity Test |
Sanity tests are subsets of the confidence test and are
used only to validate high-level functionality. |
| Security Testing |
It is a test how easy to break program's security system. |
| Server |
A computer or device on a network that manages network
resources. For example, a file server is a computer and storage device dedicated to storing files. |
| Stress Test |
These tests are used to validate software functionality
at the limit (e.g. Maximum throughput) and then testing at and beyond these limits. |
| System Level Test |
These tests check for factors such as Cross-Tool testing,
memory management and other operating system factors. |
T - u - v - w - x - y - Z
| Test |
The process of exercising a product to identify differences
between expected and actual behavior. |
| Test Requirement |
An operation, property, or behavioral characteristic
of the app-under-test that must be verified. |
| Top - Down strategy |
Start testing with the top of the program. |
| Volume Testing |
Is the process of feeding a program with heavy volume
of data. |
| Usability |
The effectiveness, efficiency, and satisfaction with
which specified users can achieve specified goals in a particular environment. Synonymous with "ease of use". |
Software Product Testing Overview...
|
|
|
|
|
 Vitamins and more...
|
 Do not forget
|
 Singles
|
 On the go
|
|
|
