This document discusses different types of software testing techniques. It outlines the typical testing workflow which involves identifying bugs through input/output testing and then fixing issues found in the code, specifications, or underlying libraries/compilers. It also describes various testing strategies like assertions to validate conditions, fault injection to test error handling, unit/integration/system testing, coverage testing to evaluate code execution, and stress testing to evaluate performance under heavy loads or edge cases. The goal is to find and address issues prior to releasing software to production.

1. Software Testing
inthra.onsap@gmail.com

2. Testing Workflow
Software Under Test
(SUT)
Input Output

3. Identify Bugs
Test code bugs
No
Yes
Function code
bugs
No
Yes
Specification
bugs
No
Yes
Compiler or Lib
bugs
No
Yes
Fix it
Fix it
Discuss about it
Fix It
or ask people
in community
Other
deeper layer

4. Assertions
• Self-checking
• Fail fast
• Pre-condition
• Post-condition
• Maintain invariant
• Note: don’t forget to turn it off in production code

5. Fault Injection
• Embrace failure
• Expect and handle failure beforehand
• More robust software

6. Variety of testing
• Unit testing
• Integration testing
• System testing/Functional testing
• Differential testing
• Stress testing
• Random testing

7. Stress testing
• Big number and overflow
• Big memory usages
• Intensive cpu usages
• Massive read/write data
• Transfer big size of packets

8. Random Testing
Random test
case generator
Function
Under Test)
OKNOT OK
Required
Domain Knowledge
Save the result
for debugging
Seed
Number
Oracles

9. Coverage Testing
• Statement Coverage (Line of Code)
• Branch Coverage (Decision)
• Loop Coverage (0, 1 and more than once)
• MC/DC Coverage (Modified Condition/Decision)
• Path Coverage
• Boundary Value Coverage (Edge Cases)

10. Thank you
Email: inthra.onsap@gmail.com
LinkedIn: www.linkedin.com/in/inthraonsap
Facebook: www.facebook.com/inthraonsap