20 + World-Leading Test Automation Experts Will Share With You Their Most Epic Secrets
Author of The Selenium Guidebook
Of all the online test automation conferences or tech conferences, I've attended, this is the first one that didn't suck and that I actually enjoyed!
*Groups of 5 or more get 20% off at checkout
Our 2017 inaugural conference attracted 751 attendees from over 46 countries and generated over 13,956 conversations in our private slack channel to date. All sessions are delivered online and recordings are available upon conclusion of each conference day within 24hrs. So you don't want to miss out on our 2018 event. Register below to get lifetime access to all conference content.
Co-author of How Google Tests Software and Founder of Appdif
Love your Guild conferences and I've pointed a lot of folks to it as the premier test automation conference.
Comment left in a 2017 Automation Guild Survey
As a tester but also as a mom of two young children, the Automation Guild Conference was the perfect format for me. I can listen to the speakers at the [most convenient] time for me, and having the videos available to refer back to any time is awesome.
Performance Testing and Program Manager at Deere
This has been probably the best "training money" I have ever spent in my 18 years with Deere and 15 years with the DoD.
We've brought the best speakers in the world to bring you the knowledge you need to stay ahead of the curve in the automation testing. Make sure to check out our all star lineup below!
You need to keep learning. One of the most rewarding ways to do this is by attending conferences. Unfortunately, sometimes it's difficult to make it to a conference due to travel costs, the price of the conference ticket, or your ability to take time off. Save yourself heaps of time by not having to travel to a conference and try to be able to fit it into your busy schedule.
At traditional conferences many times you end up missing a session you really wanted to attend. Or you forgot something that the presenter mentioned. Watch each session as many times as you like!
So you will be able to listen to the talks at your own pace.
Not just powerpoint presentations - real world examples. Our goal is to have as many high quality screen share sessions where the presenter is actually showing real world examples rather than high level slides.
With your paid registration, you’ll also have lifetime access to all the conference videos, so you can look back and watch on your own schedule. If you can’t make a Q&A session live, all live aspects of the conference will also be recorded and uploaded to the site within 48 hours.
In addition, you’ll receive access to the Automation Guild conference site and all its content for up to a year after the conference is over, affording you the opportunity to download it to your own device(s) where it can be kept for as long as you wish.
Autonomous cars were a Scifi dream not 10 years ago. A computer driving a car? No way. But it did happen, and is happening. And if scientists do it for a complicated task such as driving, can they do it for automated regression testing? In this talk we explore what is being done in the field today, but also speculate about the future: we introduce the 6 levels of autonomous testing (that correspond to the 5 levels of autonomous driving), and try and figure out what kind of help current AI techniques can bring to automated testing.
How autonomous driving works (unrelated, but fun to know!)
How AI works today to assist you in testing your app
Where can AI take us in the near term
The 6 levels of AI in automated testing
Dreaming about the long-term
Automation is a vast topic and requires a whole host of skills to get value from. Yet as an industry the only one we seem to focus on is the ability to code. This has perplexed me for a while, so recently I starting thinking about the anatomy of an automated check. Which in turn led to me thinking about the skills required for each component. The result of this thinking is S.C.A.R.E.D.
SCARED is a mnemonic to aid with the design and implementation of automated checks. SCARED is a powerful mnemonic that encourages all the team to get involved in the design of our automated checks. It sheds light on the important components that lead to reliable and valuable automation. Code is important, knowing tools is important but not as important as the non-coding skills such as modelling, system knowledge, critical thinking and communications. Those amongst many others we’ll discuss are all required for successful use of automation in the context of testing.
So, I encourage you to not be scared of automation and join me for this session. Together we will explore automated checking and discuss how the most important part in automation may very well not be the ability to code, so perhaps we start to value and appreciate these other skills, and more importantly, those people who already have them.
Manual testing is becoming increasingly more complex, causing companies to realize they can help testers be more effective and efficient at their job by automating appropriate tasks. But let’s face it: Test automation is scary and still new to many QA departments. Many are unclear about where to begin: Do you need a degree or significant development training to write automated tests? What are the programming basics and required tools that a tester needs to know?
Leo Laskin illustrates data sets of untrained Selenium and non-technical users and the time it took them to learn Selenium. Hear about the programming basics needed to be successful in QA automation and how easy it is to pick them up, the best development tool kits for Selenium and IDE programs, as well as a preview of more advanced QA topics, including CI/CD and virtualization of test environments.
Learn the challenges of appropriately applying technology to testing, great programming techniques and development tools needed to excel in automation, and how anyone who can code can cook up their own automated scripts using Selenium.
User Interface Testing of iOS app was never easy. In order to replace army of manual testers, various tools like Appium, Calabash came in picture which are just wrappers on top of Apple’s native technologies like instruments and UIAutomation to prove the point of automated simulators. Those tools allowed QA engineers to write a script in other programming languages like Ruby, Java, and so on. However, this approach proved more damaging to iOS development than good. The QA engineers use Java or Ruby to automated UI tests and developers keep developing in Objective-C or Swift. This produced huge technology gap between developers and QA engineers. There are millions other problem using those tools for testing UI of iOS app.
Apple introduced UI Testing framework embedded in Xcode IDE which is also known as XCUITest in WWDC 2015. The XCUITest framework enabled UI Tests to be written Swift, Apple’s own programming language which can be understood by both QA and Developers to bridge the technology gap. In this hands-on demo we will see how to get started with XCUITests.
Overview of XCUITest Framework (15 Min)
Practical Demo (30 min)
Practical demo covers following :
1] Setting up Example iOS project
2] Create UI Testing target within XCode
3] Exploring XCTest API’s to write UI Tests
4] Create our own UI Tests
5] Making UI Tests Scalable
6] Executing & Analysing UI Tests from Xcode
7] Executing UI Tests from command Line
At the end of this talk, you will have an understanding of XCUITest framework and should be able to write your own tests by using XCUITest API.
Manoj aims to cover the following:
(a) Overview of Webdriver Js
(b) Sample project Setup with Mocha framework
(c) Usage of Async & Await
4. Angular Introduction and Protractor in Action
(a) Blocking Proxy
(b) Protractor with TypeScript
(c) Page Objects
(d) Usage of Async/Await
A common pattern that Automator’s fall into is trying to execute every action of a test via the UI, from logging in, creating required data, navigating to that specific data and then running assertions on it before logging out. This can lead to tests that are slow to run and likely to break due to the reliance on many Web elements.
This talk will demonstrate to participants how they can use HTTP request libraries and WebDriver in harmony. We’ll cover how HTTP request libraries can take care of state manipulation and data setup so that WebDriver can be used to focus on the areas WebDriver is strongest at.
We’ll look at:
* How we design a test and what actions are involved in the execution of a test
* How we can break up the different actions of a test and assign different tasks to different libraries
* A practical demonstration of how to add an HTTP request library into a current WebDriver based framework to create data for WebDriver to use
* An approach participants can use to organise HTTP request code to make it DRY and reliable
* Tips and tricks for participants to use to help them determine what HTTP requests and WebDriver can help them with
Participants will leave with a deeper appreciation for the strengths of WebDriver and how to effectively improve their frameworks reliability and speed.
We all have to write some bits of code that seem too complicated or that take too much of our time. We wish there was a way to just have that code out of the box, and use it without much hassle. Luckily, there is a collection out there, the Apache Commons project, that provides us helper classes and methods for all kinds of tasks, like:
* Working with Strings (extracting substrings, checking whether other strings occur in a given String, splitting them)
* working with files and folders (creating, copying, moving or deleting them)
* generating random Strings of specified lengths and containing specified or random characters
* checking the OS the tests are running on
* and so many more
Join my talk, as i will present some of the most useful helper classes included in the Apache Commons libraries, together with some of their frequent uses.
If we want confidence in our software product, if we want production deployments to be boring and routine rather than fraught and stressful, we have to master test automation. Automating tests is hard. It’s expensive to automate and maintain tests. Some say “Our managers won’t let us”. Others say “I can’t find testers who are good at coding” or “I picked the wrong tool.” Yet, we see many teams are doing continuous delivery, so they must have figured out test automation. What’s the magic silver bullet? Lisa Crispin has decades of experience with successful test automation. She will reveal the secrets to success, illustrated by an infamous test automation fable.
Learning outcomes (well, they are secret, but here’s an idea):
•How to make time for innovation, and for other testing activities such as exploratory testing
•How to get the skills you need to succeed
•Why this doesn’t mean firing your testers or automating everything
You have a team dedicated to writing test cases, and you have a team tasked with automating them. So who is responsible for speaking for your tests? You would suspect this would be the added task of the engineer or the engineer in test, however wouldn’t it be great if the tests spoke for themselves?! This can be a dream realized. When a test is passing or failing, it should be indicative of a story. It should inform the team of key information in order to understand what is going on with your technology. Join me as I discuss stronger communication within your automated checks, proper messaging to clue teams in on product status, and the must haves to include in order to leave tests to advocate for themselves.
This session will cover:
* Who is DevOps?
* Why automation developers should work with DevOps?
* How automation Developers should work with DevOps?
* If there are no DevOps in your company, what should you do as an automation developer?
Are you an automation developer looking for a new position? Let’s simulate the experience of a coding interview:
Open up a browser and Google the keyword “stopwatch.”
Take out a blank piece of paper and a pen.
Press the “Start Button” on the stopwatch web app, then attempt to answer the following question:
“Using your favorite programming language: Write a method that checks to see if a given word is a palindrome. Example palindromes: ‘noon’ and ‘racecar’.”
Ready? … GO!
Yes. Seriously. Attempt to answer the question. I’ll wait.
Try this exercise for at least a good 60 seconds, even if you think you can’t do it. Don’t give up!
… Time’s up! How well did you do?
If you had trouble with this question, if your paper is mostly or completely blank, if your forehead is covered in flop sweat, or if your first thought was, “Why are you forcing me to do this? I’m an automation developer, not a coder!” then this talk is for you.
One of the most challenging parts of the software delivery lifecycle can be setting up a testing framework. It takes time, a lot of thought, and commitment to do things that will support the success of your future testing efforts. However, when you set up the right one it can help you establish everlasting success from there on out. But getting started—well that can be a very painful process. Join me in this webinar to learn how to define the important components of the SDLC, decompose and reuse common functionalities, and make informed decisions about your testing suites.
According to Gartner AWS is the leader in infrastructure as a service (Iaas). In 2017 the company I worked for at the time won the Gartner award “Best Data Management and Infrastructure”. Key to our success have been the automation tools we built to successfully run >100 deployments per day to AWS. In April 2017 we open sourced the tools. In 2017 a lot of work went into the tools to make them more robust and usable for a broader audience.
Espresso is a framework introduced by Google that provides reliable and fast automation for Android apps. We will start with setup and configuration of espresso with Android Studio. We will use the standard tooling and create a test and execute it on a local emulator and remote firebase test lab from within the IDE. Then, we will walk through locators, actions and assertions with a more complicated test. Finally the session demonstrates the synchronization of espresso through a network rule. Unlike traditional black box testing frameworks, espresso knows about the internal state of the app, system UI threads and can synchronize waiters appropriately, giving unprecedented control and accuracy for test steps.
Everyone has heard of the test automation pyramid – you should have lots of unit test automation, and less user interface tests at the top. But a lot of places are still struggling with this. Typically in reality we have more UI tests than unit ones – the “ice cream cone” reality.In this session we’ll examine a couple of scenarios, and work to build a better unit test framework. We’ll take code which has unit testing in it which isn’t that great, and apply some principles to make it better.
The key take homes will be:
* Unit testing is fast
* Everything starts with the design – we’ll look at how the code is written can aid or hamper testing
* Unit testing ideally should be simple, not elaborate, ideally testing only one thing per test.
Most session will focus on actionable automation tools and technique you could use right away. No fluff
SESSION PREVIEWS >