• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Lasse Koskela What Does It Do Does It Work
 

Lasse Koskela What Does It Do Does It Work

on

  • 1,623 views

 

Statistics

Views

Total Views
1,623
Views on SlideShare
1,622
Embed Views
1

Actions

Likes
0
Downloads
18
Comments
0

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Lasse Koskela What Does It Do Does It Work Lasse Koskela What Does It Do Does It Work Presentation Transcript

    • What does it do? Does it work? QCon London 2008 - An XpDay Sampler Lasse Koskela (c) 2008 Lasse Koskela
    • (c) 2008 Lasse Koskela
    • (c) 2008 Lasse Koskela
    • (c) 2008 Lasse Koskela
    • (c) 2008 Lasse Koskela
    • What does it do? Does it work? QCon London 2008 - An XpDay Sampler Lasse Koskela (c) 2008 Lasse Koskela
    • • how do we specify systems? • how do we test them? (c) 2008 Lasse Koskela
    • how do we test systems? (c) 2008 Lasse Koskela
    • developer testing bliss • xUnit frameworks and patterns • mock object libraries, reflection capabilities • language as common denominator (c) 2008 Lasse Koskela
    • customer testing misery • no standard toolset • tooling generally not sufficient • common denominator? (c) 2008 Lasse Koskela
    • surely there are at least some commonalities... (c) 2008 Lasse Koskela
    • tools for customer testing test tool glue system • text vs. tabular • imperative vs. descriptive (c) 2008 Lasse Koskela
    • connecting to the system • there are certain high-level patterns for • interacting with the system, and • observing side effects (c) 2008 Lasse Koskela
    • 3+2 (c) 2008 Lasse Koskela
    • 1 end to end (c) 2008 Lasse Koskela
    • 2 crawling under the skin (c) 2008 Lasse Koskela
    • 3 exercising the internals (c) 2008 Lasse Koskela
    • +2 (c) 2008 Lasse Koskela
    • 4 stubbing out the irrelevant (c) 2008 Lasse Koskela
    • 5 using testing backdoors (c) 2008 Lasse Koskela
    • how do we specify systems? (c) 2008 Lasse Koskela
    • specification analysis design implementation testing (c) 2008 Lasse Koskela
    • (c) 2008 Lasse Koskela
    • agile specification • happens during each iteration • adds detail incrementally over time • eventually evolves into automated tests (c) 2008 Lasse Koskela
    • tests as specification • running tests are ultimately the most accurate description of the system (excluding the system itself) • translation steps between a specification and tests introduces translation errors (c) 2008 Lasse Koskela
    • acceptance test driven development select feature specify tests implement automate tests feature (c) 2008 Lasse Koskela
    • who does what? (c) 2008 Lasse Koskela
    • when does it happen? (c) 2008 Lasse Koskela
    • in other words... • testers and programmers need to collaborate more closely • development team and customer need to collaborate more closely • we need a shared language and medium for doing this! (c) 2008 Lasse Koskela
    • we need an interface... test X tool system ...that lets us specify tests in our shared language (c) 2008 Lasse Koskela
    • 3 guiding principles (c) 2008 Lasse Koskela
    • 1 Avoid turbulent interfaces (c) 2008 Lasse Koskela
    • 2 Focus on meaning (c) 2008 Lasse Koskela
    • 3 Involve people (c) 2008 Lasse Koskela
    • thank you (c) 2008 Lasse Koskela