Resource
Article [7180]
General
[1032]
Acceptance
[63]
Ad Hoc
[28]
Agile, Scrum
[231]
Black Box
[117]
Bug, Defect
[258]
DB, Test Data
[274]
Environment
[42]
Functional
[115]
Glossary, Term
[74]
GUI, Usability
[98]
Integrate test
[46]
Interview, FAQ
[285]
Manual Testing
[117]
Methodology
[231]
Metrics
[327]
Mobile, Embed
[153]
Performance
[326]
Process
[194]
Requirement
[124]
Review, Static
[102]
Risk
[99]
Security Test
[215]
Standard, ISO
[179]
Test Automate
[347]
Test Case
[341]
Test Design
[69]
Test Plan
[311]
Test Manage
[227]
Test Script
[56]
Test Technique
[265]
Tool
[175]
Tool- Jmeter
[40]
Tool- Selenium
[125]
Unit Test
[166]
Web Test
[258]
White Box
[70]
Ebook [1163]
General
[277]
Acceptance
[3]
Agile, Scrum
[24]
DB Test
[76]
Development
[137]
GUI, Usability
[17]
Interview, FAQ
[9]
Java Test
[68]
Metrics
[17]
Mobile, Embed
[14]
Performance
[49]
Process
[11]
Requirement
[55]
Review, Analysis
[8]
Risk
[7]
Security Test
[71]
Standard
[20]
Test Manage
[85]
Test Automate
[84]
Tool
[8]
Unit Test
[67]
Web Test
[60]
Testing Tool [2276]
Acceptance
[25]
Agile, Scrum
[42]
Bug Tracking
[127]
Build, Release
[27]
Environment
[58]
DB, Test Data
[83]
Functional
[240]
GUI, Usability
[79]
Java Test
[71]
Metrics
[57]
Mobile, Embed
[79]
Network Test
[67]
Performance
[222]
Requirement
[62]
Review, Static
[105]
Security Test
[111]
Test Design
[52]
Test Manage
[208]
Unit, Debug
[224]
Utility, Capture
[97]
Web Testing
[234]
Video [622]
News [2773]
Webinar [914]
Certification Resource
CTAL [273]
CTEL [36]
CSTE, CSQA [198]
CSQE [41]
CMMI, TMMI [135]
PMP [114]
ITIL [67]
Six Sigma [41]
Other [81]
Forum
Forum [1935]
Book
[56]
Certification
[48]
Conference
[64]
ISTQB
[158]
QTP
[92]
Software Test
[1062]
Standard, ISO
[89]
Testing Tool
[287]
shivakumar_m13
2010.07.04 21:31:01
1866
Testing Glossary
• Acceptance criteria
The expected results or performance characteristics that define whether the test case passed or failed.
• Acceptance Testing / User Acceptance Testing
An acceptance test is a test that a user/sponsor and manufacturer/producer jointly perform on a finished, engineered product/system through black-box testing (i.e., the user or tester need not know anything about the internal workings of the system). It is often referred to as a(n) functional test, beta test, QA test, application test, confidence test, final test, or end user test
• Accessibility Testing
Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).
• Ad-hoc Testing
Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
• Agile Testing
Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm
• Alpha Testing
In software development, testing is usually required before release to the general public. This phase of development is known as the alpha phase. Testing during this phase is known as alpha testing. In the first phase of alpha testing, developers test the software using white box techniques. Additional inspection is then performed using black box or grey box techniques.
• Arc Testing / Branch Testing
A test case design technique for a component in which test cases are designed to execute branch outcomes. A test method satisfying coverage criteria that require that for each decision point, each possible branch be executed at least once.
• AUT
Application Under Test
• Authorization Testing
Involves testing the systems responsible for the initiation and maintenance of user sessions. This will require testing the Input validation of login fields ,Cookie security,and Lockout testing .This is performed to discover whether the login system can be forced into permitting unauthorised access. The testing will also reveal whether the system is susceptible to denial of service attacks using the same techniques.
• Back-to-back testing
Testing in which two or more variants of a component or system are executed with the same inputs, the outputs compared, and analyzed in cases of discrepancies
• Basis Path Testing
A white box test case design technique that uses the algorithmic flow of the program to design tests
• Benchmark Testing
Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
• Acceptance criteria
The expected results or performance characteristics that define whether the test case passed or failed.
• Acceptance Testing / User Acceptance Testing
An acceptance test is a test that a user/sponsor and manufacturer/producer jointly perform on a finished, engineered product/system through black-box testing (i.e., the user or tester need not know anything about the internal workings of the system). It is often referred to as a(n) functional test, beta test, QA test, application test, confidence test, final test, or end user test
• Accessibility Testing
Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).
• Ad-hoc Testing
Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing
• Agile Testing
Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm
• Alpha Testing
In software development, testing is usually required before release to the general public. This phase of development is known as the alpha phase. Testing during this phase is known as alpha testing. In the first phase of alpha testing, developers test the software using white box techniques. Additional inspection is then performed using black box or grey box techniques.
• Arc Testing / Branch Testing
A test case design technique for a component in which test cases are designed to execute branch outcomes. A test method satisfying coverage criteria that require that for each decision point, each possible branch be executed at least once.
• AUT
Application Under Test
• Authorization Testing
Involves testing the systems responsible for the initiation and maintenance of user sessions. This will require testing the Input validation of login fields ,Cookie security,and Lockout testing .This is performed to discover whether the login system can be forced into permitting unauthorised access. The testing will also reveal whether the system is susceptible to denial of service attacks using the same techniques.
• Back-to-back testing
Testing in which two or more variants of a component or system are executed with the same inputs, the outputs compared, and analyzed in cases of discrepancies
• Basis Path Testing
A white box test case design technique that uses the algorithmic flow of the program to design tests
• Benchmark Testing
Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
Service
New
Popular Documents
Weekly
Monthly
Yearly
Popular Download
Weekly
Monthly
Twitter
tag
web
Software Testing
Development
Bug
ISTQB
mobile
Test Automation
Selenium
tester
Interview
Test
software qa service
PM
Test Case
agile
QTP
Guide
agile testing
Software
testing
tool
mobile application testing
conference
Exam
Quality
checklist
Certification
QA
performance
web testing
process
Sql
mobile testing
outsourcing software testing
test plan
Plan
Unit Testing
Performance Testing
Questions
software testing company
framework
Sample Exam
HP
Management
security testing
Manual
Automation
Test management
Metrics
Template
security
Visitor
Member Login (IP)
208696
202898
202815105
Yesterday
Today
Total

 
 
