Automation Testing

Determines how well a product functions through a series of automated tasks,

using a variety of tools to sim ulate complex test data

Alpha Testing
1. Testing of a software product or system conducted at the developer’s site by the
customer
Automated Testing
2. That part of software testing that is assisted with software tool(s) that does not
require operator input, analysis, or evaluation.
Beta Testing
3. Testing conducted at one or more customer sites by the end user of a delivered
software product system.
Compatibility Testing
4. Determines how well a product works in conjunction with a variety of other
products, on certain operating systems, across a broad range of hardware and
component configurations and when exposed to earlier versions of the product.
Database Testing
5. Most web sites of any complexity store and retrieve information from some type of
database. Clients often want us to test the connection between their web site and
database in order to verify data and display integrity.
Error-based Testing
6. Testing where information about programming style, error-prone language
constructs, and other programming knowledge is applied to select test data capable
of detecting defaults, either a specified class of faults or all possible faults.
Exhaustive Testing
7. Executing the program with all possible combinations of values for
program variables.
Failure-directed Testing
8. Testing based on the knowledge of the types of errors made in the past that are
likely for the system under test.
Fault based testing
9. Testing that employs a test data selection strategy designed to
generate test data capable of demonstrating the absence of a set of
pre-specified faults, typically, frequent occurring faults.
Functional Localization Testing
10. Determines how well a product functions across a range of
language, localized versions are checked to determine whether
particular language translations create failures specific to that
language versions.
Heuristics Testing
11. Another term for fault-directed testing.
Hybrid Testing
12. A combination of top-down testing combined with bottom-up testing
of prioritized or available components.
 Interoperability Testing
13. Determines, to a deeper extent than compatibility testing, how well a
product works with a specific cross section of external components
such as hardware, device drivers, second-party software and even
specific operating systems and factory delivered computer systems.
Intrusive Testing
14. Testing that collects timing and processing information during
program execution that may change the behavior of the software
from its behavior in a real environment.
Install Testing
15. Determines how well and how easily a product installs on a variety of
platform configurations
Mutation Testing
16. A method to determine test set thoroughness by measuring the
extent to which a test set can discriminate the program from slight
variants of the program.

Mundane Testing
17. A test that include many simple and repetitive steps, it can be called
as Manual Testing
Operational Testing
18. Testing performed by the end user on software in its normal
operating environment.
Path coverage Testing
A test method satisfying coverage criteria that each logical path through the program is
tested. Paths through the program often are grouped into finite set of classes; one path
from each class is tested
Qualification Testing
19. Formal Testing usually conducted by the developer for the customer,
to demonstrate that the software meets its specified requirements.
Random Testing
20. An essentially black-box testing approach in which a program is
tested by randomly choosing a subset of all possible input values.
The distribution may be arbitrary or may attempt to accurately reflect
the distribution of inputs in the application environment.
Regression Testing
21. Selective re-testing to detect faults introduced during modification of
a system or system component to verify that modifications have not
caused unintended adverse effects, or to verify that a modified
system or system component still meets its requirements.
Smoke Testing
22. It is performed only when the build is ready. Every file is compiled,
linked, and combined into an executable program every day, and the
program is then put through a “smoke test”, a relatively simple
check to see whether the product “smokes” when it runs.
 Web site Testing
23. Compatibility Testing
–compatibility testing tests your web site across a wide variety
browser/operating system combinations. This testing typically exposes
problems with plug-ins. ActiveX controls, Java applets, JavaScript,
forms and frames. Currently there are over 100 possible combinations
of different windows operating systems and various versions of NE and
IE browsers. It is important to test across a large number of these to
ensure that users with diverse config don’t experience problems when
using the web site or application.
Web Site Testing
24. Content Testing
–Content Testing verifies a web site’s content such as images, clip art
and factual text.
Web site Testing
25. Database Testing
–Most web sites of any complexity store and retrieve information from
some type of database. Clients often want us to test the connection
between their web site and database in order to verify data and display
integrity.

Web site Testing

26. Functionality Testing
–Functionality testing ensures that the web site performs as expected.
The details of this testing will vary depending on the nature of your web
site. Typical examples of this type of testing include link checking, form
testing, transaction verification for e-commerce and databases, testing
java applets, file upload testing and SSL verification. For testing, which
is repetitive in nature, an automated test tool such as Rational’s Visual
Test can be used to decrease the overall duration of a test project.
Web site Testing
27. Performance Testing
–Performance Testing measures the web site performance during
various conditions. When the conditions include different numbers of
concurrent users, we can run performance tests at the same time as
stress and load tests.

28. Eight Second Rule

–Every page within a web site must load in eight seconds or less, even
for users on slow modem connections, or they risk losing their user to a
competitor site that serves pages more quickly.
Web site Testing
29. Server Side Testing
–Server side testing tests the server side of the site, rather than the
client side. Examples of server side testing include testing the
interaction between a web and an application server, checking database
integrity on the database server itself, verifying that ASP scripts are
being executed correctly on the server and determining how well a web
site functions when run on different kinds of web servers.
Web site Testing
30. Stress and Load Testing
–Load Testing, a subset of stress testing, verifies that a web site can
handle a particular number of concurrent users while maintaining
acceptable response times. To perform this type of testing use
sophisticated automated testing tools, such as Segue’s Silk Performer,
to generate accurate metrics based on overall system load and server
configuration.