Labels

Android (1) bash (2) boost (2) C (34) C++ (2) cheatsheet (2) CLion (6) css (3) Debian (33) DL (17) Docker (1) Dreamweaver (2) Eclipse (3) fail2ban (4) git (5) GitHub (4) Hacking (3) html (8) http (1) iOS (1) iPad (1) IRC (1) Java (30) javascript (3) Linux (164) Mac (19) Machine Learning (1) mySQL (47) Netbeans (4) Networking (1) Nexus (1) OpenVMS (6) Oracle (1) Pandas (3) php (16) Postgresql (8) Python (9) raid (1) RedHat (14) Samba (2) Slackware (45) SQL (14) svn (1) tar (1) ThinkPad (1) Virtualbox (3) Visual Basic (1) Visual Studio (1) Windows (2)

Tuesday 2 June 2020

Some quick comparisons between black and while box testing.

Black Box Testing:


  1. Requires No knowledge of the internal structure of program or application.
  2. Requires No programming knowledge required.
  3. The main goal is to test the behaviour of the software or application.
  4. Focused on the external or end-user perspective.
  5. Generally provide less detailed reports.
  6. Not time consuming.

White Box Testing:


  1. Requires knowledge of the internal structure of program.
  2. Requires programming knowledge.
  3. The main goal to test the internal operations of the system.
  4. Focused on code itself, its structure, conditions, paths and branches.
  5. Generally provide the most detailed reports.
  6. Extremely time consuming.

No comments:

Post a Comment

Note: only a member of this blog may post a comment.