CSE 201 Lecture Notes - Lecture 15: Gray Box Testing, Black-Box Testing, Test Automation
17 Apr 2019
School
Department
Course
Professor
Document Summary
3 views of looking at system for testing. See good (or bad) class design, patterns, duplicated code, inconsistencies in how things are represented. Can see all, but sometimes detail makes them miss broken functionality. Testers are a different breed, looking for functionality but poking underneath to make sure things are happening the way you said they would. Can see some of parts - gray box. Data in database to make sure things are being cleaned up correctly. Might be checking that ports are closed, network connections dropped, and that memory usage is staying steady. Your system is black box to users because it either does what it"s should or doesn"t. Black box testing: implementation is unknown; functions and inputs/outputs known. Glass box testing (white box): internal components or implementation known. Rely on information about how software has been designed or coded. Unit testing: testing individual routines and modules by dev or independent tester.
