Program Chair Test Automation Day 2018
During Angies keynote presentation, she will discuss the tester’s role in an artificial world, the skills needed to test and automate scenarios for such applications, and the impact that a tester can make in this space. Our world is changing. Artificial intelligence is being employed in just about all walks of life – from virtual assistants to self-driving cars. How does this new way of life impact test automation? What is our role as testers…is there even one? Of course there is! It’s a very exciting time to be in software testing. While the future of artificial intelligence is mostly unknown, remember that as testers, one of our strongest assets is being able to discover and report the unknown.
Major advances have been made in developing applications that utilize some form of artificial intelligence, but there’s not nearly as much consideration given to how to test them. In this talk, Angie will provide an overview of why it’s extremely important that these applications be tested and how today’s tester can begin to prepare and build their skillset for this new realm of software.
• Gain a better understanding of the testable features of AI
• You will examine the skills needed to test AI
• Explore the impact is that testers can have on developing AI applications
Historically, Software Testing and Software Development have always made use of automation. We have a powerful tool at our hands and it helps us to accelerate and enhance our own capabilities. However, there have been some misunderstandings that lead to unreasonable expectations. Software Testing has often been partitioned in what is called “manual” and “automated” testing. This session will have a look into some of the thinking pitfalls and explore the capabilities and limitations of automation in testing.
Many Test Automation efforts these days are struggling or failing. That is because it is not approached as a project and too often the most important question has not been asked nor answered: “Why”. Considering the answer, it is imperative to build Test Automation Solutions based on a sound Architecture, the grand plan of Test Automation. Zooming in on the ‘Why’ and the architecture, we (again) can help the efforts on becoming a success.
Is it possible to have an innovative approach to automating tests that doesn’t involve writing test cases? The speakers began to solve this challenge. How an open-source tool helped this innovative test approach become a reality. To enable comparison between test approaches a new framework was developed. Needing a real-world project to try out his theory, Mehmet joined forces with Hatim to apply the new framework and tool into the Railway sector. The results showed that within this setting, the innovative test automation tool was able to detect more faults and had a higher functional test coverage than the used manual test approach.
There is a huge, actual and difficult challenge in front of us: to produce software secured by default in fast development methodologies. This conference introduces the challenges we are facing regarding security embedding in the development lifecycle. How to face those challenges is a thin line separating the success and the failure. This conference will offer the Watson Care Manager Team how to inside IBM, the current automation status and the working lines for our future.
J.P. Morgan Asset Management’s trading platform transacts around $1 trillion annually. Fabian will explain how the firm addresses the challenge of creating high-performance, event-driven systems that make decisions in real-time using non-trivial algorithms. He will present an application design that allows simple automated end to end testing, data replay for debugging and state recovery. We will also see how this pattern is applied in a trading application with some real code examples.
Being good at a technical level is not enough anymore. Scenario thinking, analysing and being creative are getting known as the main attributes in automation testing. You need to understand the process, analyse and build a strategy from scratch. But what should that strategy be? Automation is no longer the problem, but knowing all the factors involved and combining scenarios is. Therefore ‘every project needs to be automated’ is a MYTH or a FACT?
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 do you know if you are ready for automated testing? This presentation offers a framework to assess your situation and identify any areas that need attention. It can be applied both to your project / organization and to you as an individual.
Are you a manager looking for test automators? Or, are you a tester or a developer who would like to try it out with test automation? By studying cat behaviour you can fairly well describe what a really good test automator should or should not do!
Program Chair Test Automation Day 2018
Teams switching to Agile and DevOps practices place increasing emphasis on fast-feedback. We’re aware that batching up large changes can increase the risk and there’s growing demand for repeatable, and reliable, build, test, and release pipelines. After years of testing being treated as an afterthought, it’s finally seen as an integral part of successful delivery. To keep up with the fast-paced delivery cycles extensive testing phases have to replace manual test phases with automated test suites.
As testers this approach can fit perfectly with our automation desires, often shaped by industry pressure to turn all testers into test automation engineers. People talk about “upskilling” manual testers, and the never-ending conversation about whether testers should code continues. We’re sold a dream where all boring and repetitive work is painlessly automated away to a single button push. But is it really this simple?
In this talk we’ll explore the challenges of building and maintaining test suites and take a look at some of the side-effects that can emerge from an automation-heavy test approach. Expect real life survival stories and some deep questioning of how we should respond. You’ll also learn some fundamental principles that you can apply to your own test approach to avoid automating yourself in.
If you’re interested in improving your automation technique, adapting your personal tastes and craft to test automation, or even just a creative new look at automation, come listen to the Tidy Tester’s Guide to Automation! We’ll go over making and keeping processes you love while letting go of sloppy direct automation tactics. Come enjoy the journey to stressless automation!
This talk will present experience from several test-automation projects, in which there was a need to decide what (test cases) and when to automate. Test automation may provide disappointing outcomes if not applied in the right time, and right context. This talk will also include a review of online sources and technical papers on this topic. This talk will benefit the audience in increasing the success chances of their test automation endeavours.
Ask all your questions to our keynote speakers:
– Angie Jones, Senior Automation Engineer, Twitter
– Illari Henrik Aegeter, Managing Director, House of Test
– Amy Phillips, Engineering Manager, MOO
– Dan Cuellar, Creator of Appicum
Most testing tools focus on automating the regression test, but with test tools you can do so much more! In this master class, I’ll demonstrate the other alternatives we have (as well as what have been discussed in the research community). We’ll look at code coverage tools, tools for mutation testing, automated test generation, monitoring for testing, and static analysis. After this talk, you will get a broader view on the state-of-the-art testing tools and how they can help you to reach your test goals.
One year ago we designed our shift-left architecture for performance testing in our Dutch Railways organization. Responsiveness, high capacity and robustness are key aspects of our IT systems and all require thorough testing. How can we ensure these aspects when time is under pressure in a Continuous Delivery environment? We reflect on how our approach was adopted in several projects.
This talk is about proposing a change of mindset, a change of how as testers should perceive test automation. “Back to the drawing board” mindset encourages testers to talk more about the design, ideas, implications, processes of test automation and moving aways from the tool-driven approach
Embedded software testing for railway vehicles contribute to facing many challenges. Having dealt with proper test environment based on Hardware-in-the-Loop we can focus on testing activities. For one of our projects: finally we have fixed all flaky tests and we have automatized almost everything. We look at that from the time perspective and ask the question: was it worth?
To speed up the continuous delivery process organisations automate the execution of their (regression) tests.
Integrating security tools in the development and test processes is the next step. In this presentation we start with an overview of different kind of security test tools. We’ll discuss Security-by-Design and other ways to eliminate the manual security tests and to speed up the time-to-market.
Take away: tips and tricks to integrate security testtools in your automated tests.
Developing (ATTD-style) using Gherkin-driven test automation for our backend isn’t without its challenges and past year was full of lessons learned. Today I will answer the question “Should we really automate all our requirements using Gherkin?” using three examples: two that improved our test automation in regards to coverage and flexibility, and one where we failed the standard ATDD approach in regards to documentation.
When I first demo’ed what is now called Appium at the Selenium Conference in 2012 I had no idea what I was doing starting an open source project. I knew little about how open source operated and worked behind the scenes. Thanks to the help of a great community and the advice of some seasoned open source contributors, Appium has quickly become the most popular open source mobile automation framework. Along the way, mistakes were made, lessons were learned, and occasionally we got things right. I’ve put together a collection of stories and lessons that I’d like to share with others to help everyone manage, contribute to, and consume open source software projects more effectively.
Program Chair Test Automation Day 2018