Programme Chair Test Automation Days 2019
We all know that in Agile things are going very fast. As the years go by, it just gets faster and faster and there is no sign it will slow down in future. Therefore, we need test automation to speed us up. With constant rush for new users, new features, our softer is rapidly changing and we don’t have time for regression testing, as we did just few years ago. Trends are changing. UI testing is not the only thing to be automated, API should also be covered with tests and unit tests are a standard. Even with this coverage, can we rely on the test automation only? Can the automated testing uncover all bugs, and even more important – can it uncover all risks? The common pitfall I see these days is trying to automate all, and not dedicating any (testing) time to other “ways” of testing. We often refer to manual testing as something old-fashioned. This is where exploratory testing comes into spotlight – to find defects which are not covered with automation, and which can never be covered with scripts or cannot be thought ahead.
Test Architect at Levi9 IT Services, Co-Founder at Test’RS Club
In the last decade the web made a drastic shift from simple, minimally interactive pages to highly dynamic applications that rival desktop-class software. During this shift, browsers became more advanced, and we started investing more into patterns and frameworks to helps us build apps that fully realize the potential of these advancements. But building an app is only part of the battle of shipping and maintaining an app. We must also continuously and consistently test our apps, but unfortunately, this is an often neglected step. And for good reason — testing is hard.
Testing in real browsers has historically been a non-trivial task. Toolchain setup, writing tests, resolving failures, handling flakiness, and waiting on long CI jobs add layers friction that consume precious time, lower the bar of overall quality, and mitigate continuous delivery of products. However, these difficulties should no longer deter us, as there are now modern open-source tools like Cypress, that enable fast and reliable automated browser testing while providing an unprecedented developer-friendly experience.
We’ll explore a new perspective on automated testing, so we can all continuously ship with confidence.
Senior Engineer, Cypress.io
Good product and project teams try to understand a range of different things when they’re asked to analyze product features. Are they tracking user’s activity and feedback about a feature/product? How are they validating that key/value is set correctly for various events in analytics while feature development?
In this talk, Rohit will share his experiences and challenges. He will show how his team did their analysis in order to get better insights for building the right product and adding more value to their customers.
Quality Engineer, eBay
Since 2000 test automation is on the horizon – we wanted to do it. But we failed. Somehow it was not possible to make test automation work. An investigation I did showed that real successful projects are scarce. With DEVOPS we have no choice.
Focus is often on the UI, sometimes resulting in 3000 frontend tests taking 3000 minutes.
Unit testing is still forgotten – testing the UI level is troublesome. No team effort.
The biggest danger of all. Management.
Managing Consultant, Capgemini
One year ago, PrecisionLender did not do any testing in their delivery pipelines aside from some flaky unit tests. Today, the tables have turned: we have hundreds of tests at all layers running continuously that are catching serious bugs. Come hear our transformative story to learn how you can achieve true continuous testing, too!
Software Engineer in Test, PrecisionLender
Developers, testers, and teams often struggle with designing, building and running Continuous Integration pipelines. What does your CI environment should look like? Which tools and technologies to use? What battery of tests to run? Let’s answer these questions during a hands-on session and learn how to design CI pipelines, focus on quick wins and find the best solution. Avoid pitfalls and connect your builds and tests into a pipeline without reinventing the wheel and spending days with configuration.
Masterclass: will take 2 rounds (ends at 12:50)
Lead QA Engineer, Avast Software
When it comes to automated mobile testing, we see two big challenges in practice. The first challenge is setting up a useful automation framework and the second are the high demands by CI/CD projects. In this presentation I’ll show how you can face these challenges using Behavior Driven Development (BDD). Like the Rosetta stone it will bring together three languages: of developers, testers and business stakeholders. At the same time it’s a great foundation for test automation. Let me show you…
Expert Testen, Squerist
Through a solitary Jenkinsfile, we run millions of tests in daily builds, personal builds, parallel builds against different Java versions, implementations, and platforms. This is the story of our experience leveraging continuous integration tools, iteratively simplifying our initial approach, into a solution that spans across many different servers, user scenarios, challenges and demands. It is the journey of learning and humble revision over the course of a year.
Verification Lead, IBM Canada
In large companies we use large (production like) acceptance test environments to validate the system. These environments are not only often fragile but also expensive to maintain. Due to the popularity of micro services we deploy more often, which decreases the availability of these environments. What if we skip the acceptance test environment for releasing to production? Can we still guarantee the quality of our end to end chain?
How do we know our new version is working, without verification in an end to end acceptance environment?
In this interactive session you will learn how you can mitigate the risk not having an end to end acceptance environment by use of Consumer Driven Contracts (contract testing).
Agile Test Consultant, AgiliX
In a world where everyone pursues to do everything continuously it is hard to preserve the bigger picture. Many organizations put a huge effort in Test Automation. But without having an eye for the context of process, technology and people it is easy to lose sight of the bigger picture. Context is key, so is the context of Test Automation. This session shines light on context and how to justify the effort of Test Automation within a given context.
Technical Attitude Chapter Lead, KZA
Confronted with the continuous nature of our ever growing IT landscape we require relevant test models and systems to cope. Language can be an important means to deal with this complexity especially when it involves cross-cultural communication.
You have probably heard of concepts like a ‘heartbeat mechanism’ or ‘system health monitoring’..
This session will take you on a journey pondering the question why we use these health related analogies within IT and what we can learn from them.
Test Consultant, Squerist
In real life, you have Appium test suites which you can split into small parts and execute those in parallel on different machines to get faster result, but it is still painful to have the test results at the end of test execution. One example of the most common reasons is a test might fail in the middle of the test-execution because of many reasons. On the other hand, your team leader just care to see the test result which should be summarized and displayed on one single screen. In such a case, Setting up monitoring tool is in rescue, thus you do not need to worry about failing test because you will have real time test result.
Software Engineer, Bosch
Are you having trouble getting test automation off the ground? Never-ending checklists and complicated test scripts kill innovation and productivity among testers everywhere. In short, something’s not working. Participate in this live demonstration of LEAPWORK and see automation be built and work right in front of your eyes.
Senior Product Evangelist, LEAPWORK
Programme Chair Test Automation Days 2019
Will tools and automation continue to support testing or will robots replace testers in the future? This talk sets the scene and perhaps a direction for the future of tools and automation in testing.
Right now, the software world is going “bot mad”. It looks like many jobs in the next ten to twenty years will be done by bots and those jobs will effectively disappear as career choices. Inevitably, there has been some talk of testers being replaced by bots and tools. The common response to date has been to say, “Impossible!” But I’m not sure such a kneejerk reaction is sensible.
Futurists might suggest the destination is intelligent robot testers. I’m not sure that is where we are heading. The next steps we take will not require sophisticated AI or Deep Learning. But the next generation of testing tools will force a change of thinking and culture. Our goals with tools will change too and we may then have a clearer view of where we are heading. Tools that use ML may then be part of the tester’s armoury.
This talk suggests how we might make sense of the tools landscape of the near future, where the pressure to modernise processes and automate is greatest, and what a new test process supported by tools might look like.
Principal, Gerrard Consulting
Raiffeisen is the third-largest banking group in Switzerland. To complement their in-house device farm, Raiffeisen evaluated features of different cloud-based solutions in the market. The option to set-up Testbirds device cloud on-premises convinced Raiffeisen and the banking group decided to go for a proof of value. This joint presentation will tell the story of the Raiffeisen test infrastructure, sketch the set-up of the entire project and discuss the challenges we have faced within the high security environment of a Swiss bank.
Tech lead, TestBirds
Software Engineer, Raiffeisen
In this talk I will present how we built a performance testing solution integrated with our continuous integration system. Our scenario wasn’t the most common one, so I’ll be covering the tools we chose for the task, including one we built ourselves, leveraging standard APIs in modern browsers to obtain metrics that are truthful to what the user experiences. You’ll see what we learned along the way, what worked best for us and also what didn’t.
Lead Quality Owner, OutSystems
How to carry out a transformation to a DevOps approach (implementing an infrastructure for Continuous Delivery) from scratch with a quarter-century old legacy software application as basis? How to deal with changing team structures, evolvement to a platform product and introducing a new software development process by focusing on Agile development principles?
In our presentation, we talk about challenges we had to combat, obstacles which prevented our progress and which best practice approaches have accompanied us on our journey.
Test Engineer Software, AVL List GmbH
Product Owner, AVL List GmbH
A lot has been said and written about the test automation world, tools continue to emerge and various ways on how to best benefit from automation are constantly debated.
So, I’ve embarked on a journey to study and learn what is test automation. I learned about the trends of academia, their interest in the specific activities of test automation. With 14 years of experience in testing industry, I found academia at the other end of the spectrum. While the gap between academia and industry is well known, I challenge you to take part in a challenge: fixing misconceptions and debating statements about test automation.
This session is not only a presentation, but also a debate. It’s about learning and exploring test automation without laptop or any other software involved.
Mobile Test Automation is increasingly becoming very important. Almost all web applications are responsive these days and it’s very important to test how the application works across devices. This means that it’s harder for a tester to manually run the automated tests over a list of devices to get device coverage and quicker results over every feature development.
We came up with a solution of executing tests in distributed or parallel fashion across remote devices from anywhere in the network using Appium Test Distribution.
Lead Consultant, ThoughtWorks
Senior Consultant, ThoughtWorks
We cannot imagine a life without mobile apps. Availability and functionality of these apps are crucial and still testing of these apps is too often a manual and time-consuming process. So….Automate!
In this hands-on talk, Frank demonstrates how to create readable and maintainable functional testscripts for mobile apps and websites quickly and easily using Robot Framework and Appium. Thanks to Robot Framework’s keyword driven testing, he removes the need for an extensive knowledge of java or other programming language.
We would like to tell our story of a test automation project, specifically how we transformed an existing manual test framework into an automated solution and integrated it into Continuous Integration pipelines to provide fast feedback to developers, stable nightly regression, and significantly reduced testing time for releases. Taking this project as a case study we will discuss what we learned along the way, and what a test automation engineer should look out for when designing, estimating, or building a test automation solution, while reusing pre-existing manual test frameworks.
Software Engineer in Test, Irdeto
Software Engineer in Test, Irdeto
SCRUM and Agile are hot! But if we want to provide insight in quality in both shorter delivery cycles and increasing functionality, there are some challenges around quality control in general and performance testing specifically. Performance tests take time to prepare, execute and evaluate and the skills for these tasks are often not present in a SCRUM team. So, should we take the risk and postpone or skip performance testing? No, this is how to do it right!
In this talk, Marcel will explain the concept and setup of automated performance testing and evaluation based on a customer reference case.
Performance Architect, Ymor
Do you want to produce secure software? Let’s start by securing your CI/CD pipeline! In this talk we discuss everything you need to get further in your security journey. There are a lot of relevant best practices we learned over the last few years that have shown to be effective. Want to know more? See you soon!
Principal Security Architect, Xebia
More and more information systems are transferred from on-premise architecture to the cloud, so the need for testing cloud solutions is rising rapidly. Serverless approach covers vast majority of performance and maintenance factors, but there are many challenges in testing cloud solutions, particularly testing related to the business logic. Considering the fact that Amazon is the world’s biggest cloud provider, in this presentation I will share my experience of testing AWS solutions and try to provide answers to the following questions:
– What are the differences between testing on-premise and cloud solutions?
– How can we monitor what is going on in the cloud?
– What are the ways to automate cloud system testing?
In addition, I will provide a quick overview of the set of services used on our AWS project.
Software Tester, Execom
Automation and Continuous Delivery are the buzzwords in today’s evolving IT world. In Agile teams, test automation is a “journey” which not only involves automating test cases but also the entire delivery pipeline from setting up environments to analysis and reporting. In this presentation I will narrate the tale of my journey from a performance tester to a test automation engineer. I will share my experiences, challenges and tips for evolving into a successful test automation engineer.
Operations Engineer, ING Netherlands
How long have you been in test automation? What was it like when you first started? How did the discipline of test automation get to where it is today, and where is it headed in the future? In this presentation, Dot Graham takes a look back at her 49 years in software test automation (and testing) from a personal perspective as well as a general view. She shares what she has learned from her experiences over the years, with lessons for today.
Dot started her working life by being put into a test group, where she wrote test execution and comparison programs (they weren’t called “tools” back then). In her career as a developer and then a testing and test automation specialist, she has seen many changes and has been in at the start of many initiatives to help promote both software testing and good test automation.
Each decade has had its own “hot topics” in computing, in testing and test automation. These concerns had a significant impact at the time, and sometimes still have influence today. Some things have changed dramatically over the past half century, but interestingly, some things have not changed. What might the future bring for software test automation?
Member Test Automation Days Programme Committee
Programme Chair Test Automation Days 2019