Are Your Tests Really Helping You?

Are Your Tests REALLY Helping?Sunday, October 9, 2011

Motivation Why do we test, anyway?Sunday, October 9, 2011

Bad MotivationSunday, October 9, 2011

Bad Motivation • “My boss told me to”Sunday, October 9, 2011

Bad Motivation • “My boss told me to” • “I’m a completist”Sunday, October 9, 2011

Bad Motivation • “My boss told me to” • “I’m a completist” • “I Test Frameworks”Sunday, October 9, 2011

Correct MotivationSunday, October 9, 2011

Correct Motivation • Verify CorrectnessSunday, October 9, 2011

Correct Motivation • Verify Correctness • Gain ConﬁdenceSunday, October 9, 2011

Correct Motivation • Verify Correctness • Gain Conﬁdence • CommunicationSunday, October 9, 2011

Test Types Vocabulary Break!Sunday, October 9, 2011

Functional Tests Does the overall product satisfy the the requirements?Sunday, October 9, 2011

Integration Tests Do the pieces ﬁt together?Sunday, October 9, 2011

Unit Tests Is the logic correct in that function?Sunday, October 9, 2011

Functional Understand the product.Sunday, October 9, 2011

The ToolsSunday, October 9, 2011

The Tools • BeHat (Cucumber)Sunday, October 9, 2011

The Tools • BeHat (Cucumber) • PHPSpecSunday, October 9, 2011

The Tools • BeHat (Cucumber) • PHPSpec • Keyboard, Mouse, and YouSunday, October 9, 2011

When Do They Work? • During prototyping • Focused on the product requirements • Refactoring • Regression of key features • Better for smaller teamsSunday, October 9, 2011

...Stop Helping? • Focused on the implementation • Rapidly changing functionality • Large organizationsSunday, October 9, 2011

Unit Tests Simple and to the point.Sunday, October 9, 2011

Verify Correctness • Line coverage • Branch coverage • Icky Bits-o-LogicSunday, October 9, 2011

Gain Conﬁdence • Individual functions • Variety of parameters • Works for expected interactions with collaboratorsSunday, October 9, 2011

Communication • Show how to use the function • Show expected interactions with other collaborators • Increase discoverability of possible reuseSunday, October 9, 2011

PHPUnit StandardSunday, October 9, 2011

Naming • Pick a directory just for tests • Pick a test file name suffix, ie. Test.php • Match the name of the test file to the name of the file being testedSunday, October 9, 2011

Classes • One class per test ﬁle • Name should match the ﬁle name • Extend only tested TestCase classes • No interfaces or abstract classesSunday, October 9, 2011

Functions • No private functions • Protected methods are reserved for overriding parent methods • Only provider and test methods are allowed • Make sure your provider and test methods are publicSunday, October 9, 2011

Control Structures • There should be NO control structuresSunday, October 9, 2011

PHPUnit Code Standard • AllowedFunctionOverride • ClassName • ExtraneousClass • FilenameSufﬁx • NoInterfaces • NoPrivateMethods • ProvenTestCase • TestOrProviderFunctionsOnly • TestOrProviderIsPublic • UnusedProviderSunday, October 9, 2011

PHP_CodeSniffer • CyclomaticComplexity (maximum of 1) • NestingLevel (maximum of 0) • UnnecessaryOverrideSunday, October 9, 2011

PHP_CodeSniffer Standard Available at: http://github.com/elblinkin/ PHPUnit-CodeSnifferSunday, October 9, 2011

Save Time • Test code MTTI of 0 • Reduce the connascence • Scales with growing development teamSunday, October 9, 2011

More... • Ensure only one class is under test • Avoid accessing globals • Environment variables • Conﬁguration from disk • Prevent interactions with external resources • Code Standard for TestabilitySunday, October 9, 2011

Integration For everything in-between.Sunday, October 9, 2011

You’re Paranoid • Experimenting with third-party code or service • You do not trust that your collaborators work as speciﬁedSunday, October 9, 2011

Save Time • Save Time • Discover integration issues early • Waste of Time • Time spent testing third-party codeSunday, October 9, 2011

Warning • Use them for experimentation • Consider an alert instead • Do not inﬂict them on othersSunday, October 9, 2011

Good or Bad? • Mock • Code Coverage • Manual • Automated • Copy/Paste • ReuseSunday, October 9, 2011

Review • Functional Tests • prototyping, early stage, small team • Unit Tests • can be too much for early stage • scale with a growing team size and code base • Integration Tests • only because you are paranoidSunday, October 9, 2011

Other Test Types • Performance Testing • Load Testing • Security Testing • Monitoring • LoggingSunday, October 9, 2011

• Who Am I? @elblinkin : Etsy, Inc. • Want More? http://codeascraft.etsy.com http://github.com/etsy http://elblinkin.infoSunday, October 9, 2011

http://elblinkin.info	623
http://protalk.me	30
http://bitly.com	27
http://protalk.ldev	23
http://paper.li	17
http://lanyrd.com	8
http://a0.twimg.com	5
http://192.168.0.100	3
http://coderwall.com	3
http://www.linkedin.com	2
http://dev.protalk.nl	1
http://zootool.com	1

Are Your Tests Really Helping You?

by LB Denker

Accessibility

Categories

Upload Details

Usage Rights

12 Embeds 743

Statistics