lessons from testing

Lessons from Testing

examples takenfrom

http://cyber-dojo.org@JonJagger

jon@jaggersoft.com

Thursday, 23 October 14

Avoid unnecessary burning of calories!

FizzBuzz

E09E8C snake 4

what do I notice?

Suppose we measure the average cyclomatic complexity of the code under test and the test

Higher number means more complex.

codetests

3.7 2.1>

codetests

3.7 2.1

teststests

4.3 >>

codetests

3.7 2.1

teststests

4.3NO!>>

codetests

2.1 2.1==

codetests

2.1 2.1==NO!Thursday, 23 October 14

codetests

2.0 2.1<

codetests

2.0 2.1<NO!Thursday, 23 October 14

codetests

1.0 2.1

codetests

1.0 2.1

YES<<<

17E09E8C wolf

~> Simple1.0

what do I notice most?

Duplication!

Duplication usually indicates

a missing abstraction

what do I notice now?

Duplication!

missing examples?

better test names?

different_identifier_style?differentIdentifierStyle?

that's ok!

duplication?

this is worse!

how about this?

Specific ?

21F1F3 alligator

!Thursday, 23 October 14

Specific ?

Specific :-)

Repetition ?

Repetition can indicate a missing

abstraction

Specific

Recently Used List

e.g. Recent Files...

52DE3BF3 buffalo

what do I notice?

Duplication!

What's left?

WTF?redbluegreen

e.g. Files!

56BAC947 snake

better!

better still

What do I notice now?

Duplication!

What does assertEquals()

print when it fails?

Do yourdiagnostics diagnose?

What diagnostic

do you want?

refactor

write a test fornew

functionalitywrite a test fornew functionality

make it pass

ship it!

write a test fornew

make it pass

ship it!

refactor

write a test fornew

make it pass

ship it!

refactor the diagnostic!

refactor

write a test fornew

make it pass

ship it!

refactor the diagnostic!

How about this?

Make it so!

external external

tAmockist style

mockist style

mockist styleG'

code tests

mockist style

classic style

code tests

the.law.of.demeter

which is more important?

the code or the tests?

You cannot determine the character or nature of a system within itself. Attempts to do so lead to confusion and disorder.

code and testsco-evolve

evolution is always co-evolution

testing

debugging

timeThursday, 23 October 14

debugging = removing what you don't want

if you get rid of what you don't want, will you be left with what you do want?

?Thursday, 23 October 14

testing

specification

specific.........

SummaryBurning calories - a metaphor for understandabilityTests should be simple, linear, low complexityTests should be specificLong_specific_test_names_are_ok Duplication usually means a missing abstractionRepetition can indicate a missing abstraction tooDo your diagnostics diagnose? Custom assertionsDon't cheat on test data - "String1" vs "red"Beware overusing Mockist styleCode and tests co-evolveTest at the end is often debuggingTest at the beginning as specification

code with no testsFB75B3

Lesson ONE

test code must be much simpler than the code it

lessons from testing

Software

2511 Lessons From SAP Retail Loyalty Testing

Testing for Market Rationality: Lessons from the FCOJ Marketjgsfss/Richardson.pdf · Testing for Market Rationality: Lessons from the FCOJ Market Jacob Boudoukh,a Matthew Richardson,b

Lessons Learned From CM-2 Modal Testing and … / TM--2 002-211692 Lessons Learned From CM-2 Modal Testing and Analysis Mark E. McNelis, Thomas W. Goodnight, and Kelly S. Carney Glenn

Lessons Learned From Hardware-in-the-Loop Testing of Microgrid Control Systems · 2019-09-06 · Lessons Learned From Hardware-in-the-Loop Testing of Microgrid Control Systems E

Data Collection & Field Exercises: Lessons from History · 2017. 5. 30. · Data Collection & Field Exercises: Lessons from History John McCarthy jmccarthy@aberdeen.srs.com. Testing

End-to-End Automated Testing: Lessons from Zombieland

Lessons Learned from Watching 200,000 User Testing Videosdownloads.usertesting.com/white_papers/Lessons... · Lessons Learned From Watching 200,000 User Testing Videos 11 LESSON 1

Evaluation Lessons From Live Fire Testing€¦ · Competence Instruction, Direction and Correction. CONTENTS 11 14 21 2 6 Evaluation Lessons From Live Fire Testing The F-35 Lightning

Creating Competent Testing Workforce Lessons from Experiments & Client Experiences! Pradeep Chennavajhula CEO, Edista Testing Institute 02 July 2011 |

Lessons Learned from Army Interoperability Certification ... · Lessons Learned from Army Interoperability Certification Testing Robert Boerjan CTSF Capability Set Coordinator, CTSF

Lessons Learned From Generator Destructive Testing

Lessons learned from user testing the facebook Paper app

Habitability Lessons Learned from Field Testing of a Small

STARCANADA 2013 Keynote: Testing Lessons from Hockey (The World’s Greatest Sport)

VMware Backups That Work—Lessons Learned From VADP Performance Benchmark Testing

Lessons From Lessons From Esther Lessons From Lessons From Esther

EXTENT-2016: Key Challenges and Lessons Learned from Testing a New Trading System

Lessons learned from testing prototypes in real life

Lessons Learned from Diagnostic Load Testing of 100 …onlinepubs.trb.org/Onlinepubs/trr/1992/1371/1371-013.pdf · TRANSPORTATION RESEARCH RECORD 1371 101 Lessons Learned from Diagnostic

Evaluation Lessons From Live Fire Testing