Tweet
Tweet

Slide 1

Slide 1 text

@MaritvanDijk77
 github.com/mlvandijk
 medium.com/@mlvandijk FFS - Great test automation does not absolve you from manual / exploratory testing

Slide 2

Slide 2 text

Recent years •More test automation •No more dedicated testers •No more manual testing - at all! @MaritvanDijk77

Slide 3

Slide 3 text

Automate all the things (meme) @MaritvanDijk77

Slide 4

Slide 4 text

But… •We cannot automate everything (we shouldn’t want to) •Automation cannot tell you what it’s like to actually use it @MaritvanDijk77

Slide 5

Slide 5 text

“If you don’t test it, your users will.” ~ @lanettecream @MaritvanDijk77

Slide 6

Slide 6 text

Tested components @MaritvanDijk77 Unit Unit Unit Integration Integration

Slide 7

Slide 7 text

Tested components @MaritvanDijk77 Unit Unit Unit Integration Integration

Slide 8

Slide 8 text

Tested whole? @MaritvanDijk77 Unit Unit Unit Integration Integration

Slide 9

Slide 9 text

Here be bugs Tested whole? @MaritvanDijk77 Unit Unit Unit Integration Integration

Slide 10

Slide 10 text

Example: Rebuilding a workflow system + Familiar with process + Close cooperation with BA + Unit tests + Integration tests @MaritvanDijk77

Slide 11

Slide 11 text

Overview Workflow System Other System Other System Other System

Slide 12

Slide 12 text

E2E Test •Notoriously difficult: •Consistent state in several systems •Collaboration between teams/depts •Hard to automate / maintain @MaritvanDijk77

Slide 13

Slide 13 text

Pair testing •Technical knowledge (dev) •Functional knowledge (test) •Less error prone •No time wasted on reproduction •Quickly fixed @MaritvanDijk77

Slide 14

Slide 14 text

Test your code! https://www.redbubble.com/people/hogfish @MaritvanDijk77

Slide 15

Slide 15 text

@MaritvanDijk77
 github.com/mlvandijk
 medium.com/@mlvandijk FFS - Great test automation does not absolve you from manual / exploratory testing