People and automation – a conversation UX? What about TX for Test Automation? Are we technical enough? Are the problems that people report with tool adoption a problem of testers not being technical enough or of tools not being easy to use? Are we over emphasising the technical and ignoring the personal?

1. People and automation
– a conversation
UX? What about TX for Test
Automation? 27-28 February 2017
LONDON
Isabel
Evans
Freelancer
Alan
Richardson
Compendium
Developments
EvilTester.com

2. 27-28 February 2017
LONDON
“Automation and people”
Are we technical enough? Are the
problems that people report with tool
adoption a problem of testers not
being technical enough or of tools
not being easy to use? Are we over
emphasising the technical and
ignoring the personal?

3. The conversa,on: “Automa,on and people”
Isabel’s theory:
• Test automa,on requires considera,on of the User
eXperience (UX) for the tool and the tests;
• People who use automa,on might not always be
technical but they are always human;
• UX-Design and UX-Tes,ng for test automa,on
supports improved decision making and quality.
Is this correct?

4. The conversa,on: “Automa,on and people”
• Are we technical enough?
• Are the problems that people report with tool adop,on a problem of testers not
being technical enough or of tools not being easy to use?
• Are we over emphasising the technical and ignoring the personal?
Join the conversa,on with Alan and Isabel where we'll talk about stuff like …

5. The conversa,on: “Automa,on and people”
Join the conversa,on with Alan and Isabel where we'll talk about stuff like:
• What levels of technical skills, knowledge and ability are required for
systems development, and specifically for tes,ng ac,vi,es?
• What do we mean by “Technical”? – just Technical (IT) or also Technical
(Domain)?
• What types of technical knowledge support our tes,ng (for example
technical architecture, hardware as well as soUware, code, etc).

6. The conversa,on: “Automa,on and people”
Join the conversa,on with Alan and Isabel where we'll talk about stuff like:
• How do we keep up to date with the technology we test? If not, why not?
• If the ‘technical people’ on the team don’t understand the system, how
do we iden,fy technical risks?
• As the toolset we use matures, can we rely on it to support people beXer,
or are the people driven by the technology they use?
• How do we improve the Tester's Experience of automa,ng and working
with more technical systems?

7. 27-28 February 2017
LONDON
Website: www.isabel.evans.uk
Stories: h5ps://isabelevanswri8ng.wordpress.com/
Blog:
h5ps://isabelevansconsultancy.wordpress.com/
Linked in: h5ps://uk.linkedin.com/in/isabelevans
Twi5er: @IsabelE_Test

8. 27-28 February 2017
LONDON
- Linkedin - h5ps://uk.linkedin.com/in/eviltester
- Twi5er - h5ps://twi5er.com/eviltester
- Instagram - h5ps://www.instagram.com/eviltester
- Facebook - h5ps://facebook.com/eviltester/
- Youtube - h5ps://www.youtube.com/user/EviltesterVideos
- Pinterest - h5ps://uk.pinterest.com/eviltester/
- Github - h5ps://github.com/eviltester/
- Slideshare - www.slideshare.net/eviltester
Alan Richardson
www.eviltester.com
www.seleniumsimplified.com
www.javafortesters.com
www.compendiumdev.co.uk