Just a few slides, and then in to live coding tests in to a legacy application!
We're go over adding a Selenium test first, and then a Unit test, and then refactor with confidence!
2. WHAT THIS TALK ISN'T
!
> About TDD
> Framework Specific
> For testing veterans
3. WHAT THIS TALK IS
!
> An introduction to testing jargon
> A collection of techniques for starting to test your
app
> Introduction to Selenium and TestBox
> Asking tough questions as well as giving answers
4. OTHER SESSIONS RIGHT NOW
> Lucee Panel Discussion — Room 235
> Writing Highly Organized CSS — Room 238
> Ouch, It Hurst When Do That. A Tale Of Landmines And
Self-Inflicted Wounds — Room 321
> Getting Started With Build Tools — Auditorium
5. WHO AM I?
ERIC PETERSON
! Utah
" O.C. Tanner
# 1 wife, 1 kid
6. WHAT KIND OF THINGS MAKE AN APP A
LEGACY APP?
> No framework
> Few or no tests
> Old or incorrect design decisions
> New or changed business requirements
13. MY LEGACY APP TESTING PHILOSOPHY*
(* SUBJECT TO CONSTANT CHANGE !)
> Don't stress about the kinds of tests you are writing.
Slow tests are better than no tests
> Utilize Continuous Integration to offset this
> Split your tests up and create multiple runners to help
as well.
14. MY TESTING PHILOSOPHY
TEST WHAT MAKES SENSE (AND WHAT SAVES YOU
MONEY)
SOME EXAMPLES:
> It broke before
> We test it manually every time
> The logic is kind of hard to follow (for the next time
15. MY TESTING PHILOSOPHY
TDD
> Helps you design the class one piece at a time (not
focused on in this talk)
> Pair programming (one writes the test, the other writes
the code to make the test pass)
16. BEST TYPES OF TESTS FOR A LEGACY APP?
Integration Testing
&
Regression Testing
17. BEST TOOLS TO TEST A LEGACY APP?
> Selenium
> TestBox
> Travis