Test Driven Development

Test Driven Development

1. Verification

   • Dynamic Verification (testing your code)
     • Runtime Verification
       • Checking tests and software as you go
     • Create tests to make the system fail
       • Finds errors before production/deployment
       • Preventative testing
   • Inspections/Reviews/Walkthroughs
     • Human Reviews
     • Manual testing
       • Has a checklist/formal and informal methods
     • Allows for feedback and improvement
   • Static Verification
     • Checks code in background
     • Code does not need to run for these tests to run
     • Checks code before runtime or compile time
     • Looks for potential issues/also a preventative testing method
   • Formal Verification
     • Extremely math-based
     • The most formal method
       • Checks for specification
     • Potentially time-consuming and expensive
     • Relies on detailed information and "manual" for testing

2. Stages

   • Developer's and Alpha Testing
     • Proofreading before integrating into entire project
   • Beta and Product Testing
     • User's start using the application for feedback and catch any bugs or issues

3. Make it Fail, Make it Work, and Make it Better