Presented at Agile Testing Days US 2018 https://agiletestingdays.us/

1. KeepingYour
TestsLeanMeaghanLewis
@iammeaghanlewis

2. What does
LEAN
mean anyway?

3. VALUABLE
RELIABLE
FAST

4. 1000+ tests

5. 12 hour build

6. 100% failure rate

8. How did we get a LEAN
test suite?

10. Not quite…

12. VALUABLE

13. TESTS CAN GET OUTDATED

14. Ideas for valuable tests

15. Re-evaluate & Analyze
• Whatisthistestdoing?
• Whatvalueisthistestproviding?
• Isthistestingtherightthing?

16. Quality vs. Quantity

17. Collaborate on testing

18. Treat test code like production code
• Writeinsamelanguage
• Keeptestsinsamecodebase
• Followthesamerules

19. RELIABLE

20. Even one failure makes a difference

21. Ideas for reliable tests

22. Isolate flaky tests
Isolate
flaky tests
Analyze Fix
Move back
To build

23. Monitor flakiness
Automaticallyrecordtestfailures
Test Name Error # Failures
testUserCreation ElementNotFoundException 3

24. Automatically rerun failures

25. Use specific test selectors

26. Independent tests
• Testsshouldallbehermetic
• Executionofonetestdoesnotaffectanother
• Runindedicatedtestingenvironment

27. FAST

28. Test runs shouldn’t feel like a marathon

29. Continuous deployment pipeline
Goal: Makeeachstepasfastaspossible
Unit &
Integration
Tests
Deploy to
Staging
UI Tests
Deploy to
Production

30. Ideas for fast tests

31. Parallelize tests
Test 1 Test 2 Test 3
Test 1
Test 2
Test 3
Sequential
Parallel

32. Avoid testing in the UI

33. Headless tests
• RunbrowsertestswithoutthebrowserGUI
• GreatforCIandremoteservers
• Tools:PhantomJS,HeadlessChrome,Puppeteer

34. REMEMBER…

35. There are tradeoffs

36. It’s okay to start over

37. Testing is a team effort

38. Thanks!
@iammeaghanlewis
linkedin.com/in/meaghan-lewis
meaghanlewis.com