The technique of testing without having any knowledge of the interior workings of the application is called black-box testing. The tester is oblivious to the system architecture and does not have access to the source code. Typically, while performing a black-box test, a tester will interact with the system’s user interface by providing inputs and examining outputs without knowing how and where the inputs are worked upon.
White-box testing is the detailed investigation of internal logic and structure of the code. White-box testing is also called glass testing or open-box testing. In order to perform white-boxtesting on an application, a tester needs to know the internal workings of the code.
The tester needs to have a look inside the source code and find out which unit/chunk of the code is behaving inappropriately. Grey-box testing is a technique to test the application with having a limited knowledge of the internal workings of an application. In software testing, the phrase the more you know, the better carries a lot of weight while testing an application.
- Software Application
- Development of Software Application
- Introduction to Software Testing
- Process of Testing
- Test Design for Functional Testing
- Test Execution
- Defect Management
- Other Testing Types
- Quality and Process Improvements
- Introduction to Automation Testing
- Selenium IDE – Record – Edit- Playback
- Selenium IDE – Debugging
- Selenium IDE – Commands
- Selenium RC
- Getting Started with Bugzilla
- Bug Life Cycle
- Bugzilla Searching Bug
- Reports and Charts