ALL Types of Software Testing
I am NOT Responsible for any Errors - Use at your own risk
Last Updated: 4/18/2017
TESTING QA - Complete Acronyms/Glossaries Programming & Design SAN - NAS - Storage - Virtualization
These snippets are mostly taken from Wikipedia - SOFTWARE TESTING
ALL OF THIS WEB PAGE IS A SUB-SET OF MY TESTING-QA WEB PAGE
My TESTING BOOKS are listed here (you can search the page).
ACCESSABILITY TESTING
coming soon...
ALPHA TESTING
"Alpha testing is simulated or actual operational testing by potential users/customers
or an independent test team at the developers' site. Alpha testing is often employed
for off-the-shelf software as a form of internal acceptance testing, before the software
goes to beta testing." Alpha Testing - WikipediaAUTOMATION TESTING
Automation Test Suites
Script Testing
BETA TESTING
"Beta testing comes after alpha testing and can be considered a form of external user
acceptance testing. Versions of the software, known as beta versions, are released
to a limited audience outside of the programming team. The software is released to
groups of people so that further testing can ensure the product has few faults or bugs.
Sometimes, beta versions are made available to the open public to increase the feedback
field to a maximal number of future users." - Beta Testing - Wikipedia
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.
CLEAR BOX TESTING = Glass Box Testing = White Box Testing
CLEAR BOX TESTING (White-box, also Glass-box) testing is a method of testing software
that tests internal structures or workings of an application, as opposed to its
functionality.
In clear-box testing an internal perspective of the system, as well as programming
skills, are used to design test cases. The tester chooses inputs to exercise paths
through the code and determine the appropriate outputs.
COMPATABILITY TESTING coming soon...
DESTRUCTIVE TESTING TESTING
"Destructive testing attempts to cause the software or a sub-system to fail. It verifies
that the software functions properly even when it receives invalid or unexpected inputs,
thereby establishing the robustness of input validation and error-management routines.
Software fault injection, in the form of fuzzing, is an example of failure testing.
Various commercial non-functional testing tools are linked from the software fault
injection page; there are also numerous open-source and free software tools available
that perform destructive testing." - Destructive Testing - Wikipedia
DVT (Design Verification Testing)
coming soon...
EMBEDDED TESTING
coming soon...
FAULT INSERTION TESTING
coming soon...
FINAL PRODUCT TESTING
coming soon...
FIRMWARE TESTING
coming soon...
FUNCTIONAL TESTING
"Functional testing refers to activities that verify a specific action or function of the code.
These are usually found in the code requirements documentation, although some development
methodologies work from use cases or user stories. Functional tests tend to answer the question
of "can the user do this" or "does this particular feature work." - Functional Testing - Wikipedia
GLASS BOX TESTING
GLASS BOX TESTING (Clear-box, also called White-box) testing is a method of testing
software that tests internal structures or workings of an application, as opposed
to its functionality.
In Glass-box testing an internal perspective of the system, as well as programming
skills, are used to design test cases. The tester chooses inputs to exercise paths
through the code and determine the appropriate outputs.
GRAY (Grey) BOX TESTING
"Gray-box testing (International English spelling: grey-box testing) is a combination of
white-box testing and black-box testing. The aim of this testing is to search for the
defects if any due to improper structure or improper usage of applications." - Gray box testing - Wikipedia
Gray Box Testing - Tests involving inputs and outputs, but test design is educated by
information about the code or the program operation of a kind that would normally be
out of scope of view of the tester.[Cem Kaner]
GUI TESTING
I like Selenium.
HARDWARE TESTING
coming soon...
INSTALLATION TESTING
coming soon...
INTEROPERABILITY TESTING
coming soon...
LOAD TESTING
"constantly increasing the load on the system via automated tools. For a Web
application, the load is defined in terms of concurrent users or HTTP connections.
In the testing literature, the term "load testing" is usually defined as the
process of exercising the system under test by feeding it the largest tasks it
can operate with. Load testing is sometimes called volume testing, or longevity/
endurance testing." - http://agiletesting.blogspot.com
MANUAL TESTING
coming soon...
NEGATIVE TESTING
In software testing, a test designed to determine the response of the system
outside of normal parameters. It is designed to determine if the system
performs error handling with unexpected input.
Negative test - Wikipdeia
NON FUNCTIONAL TESTING
Non-functional testing refers to aspects of the software that may not be related
to a specific function or user action, such as scalability or other performance,
behavior under certain constraints, or security. Testing will determine the flake
point, the point at which extremes of scalability or performance leads to unstable
execution. Non-functional requirements tend to be those that reflect the quality
of the product, particularly in the context of the suitability perspective of its
users - Functional Testing - Wikipedia
OUT OF THE BOX EXPERIENCE TESTING
coming soon...
PENETRATION TESTING
coming soon...
PERFORMANCE TESTING
"The goal of performance testing is not to find bugs, but to eliminate bottlenecks
and establish a baseline for future regression testing. To conduct performance
testing is to engage in a carefully controlled process of measurement and
analysis. Ideally, the software under test is already stable enough so that this
process can proceed smoothly. - http://agiletesting.blogspot.com
Performance testing is generally executed to determine how a system or sub-system
performs in terms of responsiveness and stability under a particular workload.
It can also serve to investigate, measure, validate or verify other quality
attributes of the system, such as scalability, reliability and resource usage.
REAL-TIME TESTING
coming soon...
REGRESSION TESTING
coming soon...
SMOKE TESTING
coming soon...
STRESS TESTING
Stress testing tries to break the system under test by overwhelming its resources
or by taking resources away from it (in which case it is sometimes called negative
testing). The main purpose behind this madness is to make sure that the system fails
and recovers gracefully - this quality is known as recoverability. http://agiletesting.blogspot.com
UAT TESTING (User Acceptance Testing)
In engineering and its various subdisciplines, acceptance testing is
a test conducted to determine if the requirements of a specification or
contract are met. It may involve chemical tests, physical tests, or
performance tests.
In systems engineering it may involve black-box testing performed on a
system (for example: a piece of software, lots of manufactured mechanical
parts, or batches of chemical products) prior to its delivery.
Software developers often distinguish acceptance testing by the system
provider from acceptance testing by the customer (the user or client)
prior to accepting transfer of ownership. In the case of software,
acceptance testing performed by the customer is known as user acceptance testing
(UAT), end-user testing, site (acceptance) testing, or field (acceptance) testing.
Acceptance testing - Wikipedia
UX TESTING (User Experience / Userability Testing)
"Usability testing is a technique used in user-centered interaction design to evaluate a
product by testing it on users. This can be seen as an irreplaceable usability practice,
since it gives direct input on how real users use the system.
This is in contrast with usability inspection methods where experts use different methods
to evaluate a user interface without involving users. - Usability testing - Wikipedia
The Top 5 User Testing Methods Of UX Professionals
VERIFICATION TESTING
coming soon...
VISUAL TESTING
coming soon...
WEB TESTING
coming soon...
WHITE BOX TESTING = Clear Box Testing = Glass Box Testing
"White-box testing (also known as clear box testing, glass box testing, transparent box
testing, and structural testing) is a method of testing software that tests internal
structures or workings of an application, as opposed to its functionality (i.e. black-box
testing). In white-box testing an internal perspective of the system, as well as
programming skills, are used to design test cases." - White-box testing - Wikipedia
===
SCRIPTING
SCRIPTING / SCRIPTING LANGUAGES
OTHER INFORMATION
- TOP OF THIS WEB PAGE
- Acronyms / Glossary
- Woodsmall's Recommended Technical Books
- Buses & Networks, other
- Digital - DVD, Music, Recording, Video
- Embedded / Firmware / Real-Time / Drivers
- Ethernet, Cloud, 802.11x, 40GbE, 100GbE, Fast Ethernet, Gigabit Ethernet, isoEthernet
- Fibre Channel
- IP, IPsec, IPv4, IPv6, FCIP, iFCP, PPP, SoIP, TCP, TCP/IP, TOE, VoIP, Device Discovery
- Linux
- NetWare
- Organizations
- Pharma / Bioinformatics
- Programming, Agile, C, C++, Design, Algorithms, Patterns, OO, Refactoring, ADO
- Recommended Computer Security Steps
- REFERENCES
- References - Other, Postage, Converters, Dictionaries, Languages
- SAN / NAS / SATA / Storage / CIM
- SCSI / iSCSI / RAID / SAS / SMI-S
- Security, Computer
- Security, Recommendations
- Standards
- Technical Info
- UNIX
- Virus Info
- TIME, TIME ZONE INFO
- Web Development: C#, CSS, DHTML, HTML, Java, JavaScript, Perl, Python, Ruby, VSGML, VBScript, VRML, XML,...
- Windows Tips
- Wireless / PDA
OTHER SITE INFORMATION
I am NOT Responsible for any Errors - Use at your own risk