Today I am going to discuss about the testing methodology, there is two type testing methodology one is White Box Testing and second one is Black box testing.
White Box Testing:
- White Box Testing (also called as Clear Box Testing, Glass Box Testing and Transparent Box Testing or Structural Testing) is a method of testing software that tests internal structures or workings of an application.
- It is usually done at the unit level.
- White Box Testing is the verification technique software engineers can use to examine if their code works as expected
Black box Testing: An approach of testing where application/software is considered as a black box.
- Specific knowledge of the application's code/internal structure and programming knowledge in general is not required.
- Test cases are built around user specifications and requirements, gathering the data of project from the client and use this data during testing.
Types of Black Box Testing:
1. Functional Testing
2. Performance Testing
3. Security Testing
4. Compatibility Testing
5. Usability Testing
6. Negative Testing
7. Ad-Hoc Testing
Whether the application/module is functioning according to the stated requirement.
Performance testing is generally to determine the speed or effectiveness of a Network,computer, or software programs. The main task of performance how fast system.
Security testing is conducted to examine an application from the point of view of possibility to affect the user safety and/or make his/her data available from external source. This testing is especially important for payment systems and other applications which use critical data about a user.
Example: User Access Level in Application and Update Bank Account as per the Role.
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.Compatibility testing can be automated using automation tools or can be performed manually and is a part of non-functional software 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.”
Any testing carried out by passing Non-Recommended values with an aim of breaking down the application is called negative testing".