Designing Test Architecture That Does Not Suck

By: Michael Bodnarchuk

Every PHP application needs its policy about tests. What is important to test, what is not, at which levels should a feature be tested. As we think of application architecture before writing a single line of code, we should think of a test architecture before implementing tests. From this talk you will learn:

  • how to transform business expectations to tests using ATDD and BDD approaches
  • how (and why) to incorporate all testing levels (acceptance, functional, integration, unit)
  • how to prioritize tests
  • how to write stable tests that won’t be the stick in the wheel
  • how to deal with test data
  • how to decide, should it be unit or integration test
  • how to choose the type of a test