BlackBox Testing Type:
1. Functional Testing
2. Performance Testing
3. Compatibility Testing
4. Usability Testing
5. Negative Testing
6. Ad-Hoc Testing
7. Exhaustive Testing
Functional Testing:
Whether the application/module is functioning according to the stated requirement.
Performance Testing:
Performance testing is the process of determining the Speed or effectiveness of a computer, Network, Software Program or Device. This process can involve quantitative tests done in a lab, such as measuring the response time or the number of MIPS (millions of instructions per second) at which a system functions. Qualitative attributes such as reliability, scalability and interoperability.
.
Compatibility Testing:
Compatibility testing is a type of testing used to ensure compatibility of the system/application/website built with various other objects such as other web browsers, hardware platforms, users (in case if it’s very specific type of requirement, such as a user who speaks and can read only a particular language), operating systems etc. This type of testing helps find out how well a
SQT & Quality Course Contents Page 8
system performs in a particular environment that includes hardware, network, operating system and other software etc.
Compatibility testing can be automated using automation tools or can be performed manually and is a part of non-functional software testing.
Usability Testing:
Negative Testing:
Any testing carried out by passing Non-Recommended values with an aim of breaking down the application is called negative testing".
"If a developer designed an edit box to accept only numeric value up to length of 10 numbers and if we entered the alphabets and alphabets are accepted by the Text Box then it is called as negative testing"
Ad Hoc Testing:
Testing without a formal test plan or outside of a test plan. With some projects this type of testing is carried out as an adjunct to formal testing. If carried out by a skilled tester, it can often find problems that are not caught in regular testing. Sometimes, if testing occurs very late in the development cycle, this will be the only kind of testing that can be performed. Sometimes ad hoc testing is referred to as exploratory testing.
Exhaustive Testing:
Exhaustive testing is the testing where we execute single test case for multiple test data. Exhaustive testing means testing the functionality with all possible valid and invalid data.
Test to verify the behavior of every aspect of an application, including all permutations. We execute a program with all possible combinations of inputs or values for program variables. Generally we use Automation testing when single test case executed for multiple test data
1. Functional Testing
2. Performance Testing
3. Compatibility Testing
4. Usability Testing
5. Negative Testing
6. Ad-Hoc Testing
7. Exhaustive Testing
Functional Testing:
Whether the application/module is functioning according to the stated requirement.
Performance Testing:
Performance testing is the process of determining the Speed or effectiveness of a computer, Network, Software Program or Device. This process can involve quantitative tests done in a lab, such as measuring the response time or the number of MIPS (millions of instructions per second) at which a system functions. Qualitative attributes such as reliability, scalability and interoperability.
.
Compatibility Testing:
Compatibility testing is a type of testing used to ensure compatibility of the system/application/website built with various other objects such as other web browsers, hardware platforms, users (in case if it’s very specific type of requirement, such as a user who speaks and can read only a particular language), operating systems etc. This type of testing helps find out how well a
SQT & Quality Course Contents Page 8
system performs in a particular environment that includes hardware, network, operating system and other software etc.
Compatibility testing can be automated using automation tools or can be performed manually and is a part of non-functional software testing.
Usability Testing:
- Checks whether the layout, text and the messages displayed are user friendly and meet the stated requirement.
- Cursor is properly positioned, Navigation of cursor.
- On-line list displayed in proper sort sequence.
- Project screen standards are adhered to (i.e., colors, common field lengths, protected fields, error highlighting, cursor position, etc.)
- “Usability Testing is needed to check if the user interface is easy to use and understand.”
Negative Testing:
Any testing carried out by passing Non-Recommended values with an aim of breaking down the application is called negative testing".
"If a developer designed an edit box to accept only numeric value up to length of 10 numbers and if we entered the alphabets and alphabets are accepted by the Text Box then it is called as negative testing"
Ad Hoc Testing:
Testing without a formal test plan or outside of a test plan. With some projects this type of testing is carried out as an adjunct to formal testing. If carried out by a skilled tester, it can often find problems that are not caught in regular testing. Sometimes, if testing occurs very late in the development cycle, this will be the only kind of testing that can be performed. Sometimes ad hoc testing is referred to as exploratory testing.
Exhaustive Testing:
Exhaustive testing is the testing where we execute single test case for multiple test data. Exhaustive testing means testing the functionality with all possible valid and invalid data.
Test to verify the behavior of every aspect of an application, including all permutations. We execute a program with all possible combinations of inputs or values for program variables. Generally we use Automation testing when single test case executed for multiple test data
No comments:
Post a Comment