Chris Kenst – How I Became an Automation Engineer

I’ll be sharing my experiences on how I became an Automation Engineer and what that first year has looked like: the good, bad and the ok.- There’s no great definition for what an Automation Engineer should do, but in my first year I’ll show you all the ways I’ve been asked to test things

Main Takeaways:

– Test Automation doesn’t just mean writing UI automation but it does include it. It also means writing at the API and maybe even at the unit level.
– Turns out the best way to automate something is to explore it first. I’ll share the % of time I’m automating vs testing.
– Where I think my skills will go and what will be required in the future.


View session recordings:


OnlineTestConf is brought to you byPractiTest - Test Management Solution