Tweet
Tweet

Slide 1

Slide 1 text

Ten Tips for Web UI Automation Testing (Or how to succeed instead of suck) ? ?

Slide 2

Slide 2 text

Jim Holmes Guidepost Systems [email protected] @aJimHolmes http://bit.ly/leadershipjourney

Slide 3

Slide 3 text

Goals for this session

Slide 4

Slide 4 text

Get ideas on what to go back home and learn

Slide 5

Slide 5 text

Area One: Focus on Business

Slide 6

Slide 6 text

Tip 1: Automate high value workflows

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

There’s much you can automate

Slide 10

Slide 10 text

There’s little you should

Slide 11

Slide 11 text

Tip 2: Set expectations up and down

Slide 12

Slide 12 text

You need time

Slide 13

Slide 13 text

You need resources

Slide 14

Slide 14 text

You need people

Slide 15

Slide 15 text

Tip 3: Invest in selecting right toolset for your team

Slide 16

Slide 16 text

What’s your goal for automation?

Slide 17

Slide 17 text

What’s your team’s skills?

Slide 18

Slide 18 text

Who’s creating automation? Who’s maintaining it?

Slide 19

Slide 19 text

Who’s using automation?

Slide 20

Slide 20 text

Area Two: Focus on Technical

Slide 21

Slide 21 text

Tip 4: Learn your system’s Locators

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

Tip 5: Learn your system’s Asynch

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

Tip 6: Create Helpers

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

Tip 7: Configure system for testing

Slide 29

Slide 29 text

How do you automate tests for CAPCHA ?

Slide 30

Slide 30 text

Don’t

Slide 31

Slide 31 text

Area Three: Focus on Communication

Slide 32

Slide 32 text

Tip 8: Get serious about Collaboration

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

Tip 9: Communicate Early

Slide 35

Slide 35 text

The best testing happens before a single line of code is written

Slide 36

Slide 36 text

Tip 10: Get fanatical about Feedback Loops

Slide 37

Slide 37 text

Whole Team Testing means TALK TO SUPPORT

Slide 38

Slide 38 text

Retrospectives

Slide 39

Slide 39 text

FAILURES

Slide 40

Slide 40 text

Thank You!

Slide 41

Slide 41 text

Jim Holmes Guidepost Systems [email protected] @aJimHolmes http://bit.ly/leadershipjourney