Software Testing Methods

Testing Methods

Black Box Testing

• Testing without knowledge of the internal workings of the system
• Focus on input and output
• Types:
  • Equivalence Partitioning: divide input into partitions and test each partition
  • Boundary Value Analysis: test at the boundaries of the input partitions

White Box Testing

• Testing with knowledge of the internal workings of the system
• Focus on the code and logic
• Types:
  • Statement Coverage: ensure each statement is executed
  • Decision Coverage: ensure each decision is executed
  • Path Coverage: ensure each path is executed

Gray Box Testing

• Combination of black box and white box testing
• Tester has some knowledge of the internal workings of the system
• Focus on the interactions between components

Unit Testing

• Testing individual units of code (functions, methods, etc.)
• Focus on ensuring each unit works as expected
• Typically done by the developer who wrote the code

Integration Testing

• Testing how individual units work together
• Focus on ensuring the interactions between units work as expected
• Typically done by a separate team or person

System Testing

• Testing the entire system as a whole
• Focus on ensuring the system meets the requirements and works as expected
• Typically done by a separate team or person

Acceptance Testing

• Testing to ensure the system meets the acceptance criteria
• Focus on ensuring the system is ready for release
• Typically done by the end-users or customers

Testing Methods

Black Box Testing

• Testing approach that focuses on input and output without knowledge of internal system workings
• Equivalence Partitioning: dividing input into partitions and testing each partition
• Boundary Value Analysis: testing at the boundaries of input partitions

White Box Testing

• Testing approach that involves knowledge of internal system workings and focuses on code and logic
• Statement Coverage: ensuring each statement is executed
• Decision Coverage: ensuring each decision is executed
• Path Coverage: ensuring each path is executed

Gray Box Testing

• Combination of black box and white box testing
• Tester has some knowledge of internal system workings
• Focus on interactions between components

Unit Testing

• Testing individual units of code (functions, methods, etc.)
• Focus on ensuring each unit works as expected
• Typically done by the developer who wrote the code

Integration Testing

• Testing how individual units work together
• Focus on ensuring interactions between units work as expected
• Typically done by a separate team or person

System Testing

• Testing the entire system as a whole
• Focus on ensuring system meets requirements and works as expected
• Typically done by a separate team or person

Acceptance Testing

• Testing to ensure system meets acceptance criteria
• Focus on ensuring system is ready for release
• Typically done by end-users or customers