Keynote
|
State of the Union
Abstract:
What will Selenium 4 look like? What’s been happening in the world of Selenium since the last conference? What’s will happen to the project in the future? What lessons can we learn from the past, and how do we apply these? Why would one person work on the same project for 13 years? In this keynote, Simon will discuss not only the practical aspects of the project, but some of the philosophy that guides the project forward. Bio:
Simon Stewart is the lead of the Selenium project, and one of its core developers. He’s the creator of the WebDriver API, and the co-editor of the W3C WebDriver standard. |
Simon Stewart
|
Keynote
|
Clean
code that works - How can we go there?
Abstract:
"Clean code that works" means the sense of value and the goal of programmers. It is not easy to implement it from the beginning. In this speech, you will get to know how obstacles appear on the way to "Clean code that works" and how to resolve them. Also, I will reconfirm role and value of automation testing and refactoring. Bio:
Takuto works hard to diffuse TDD culture through writing books, speaks at several places and hands-on. He studied software engineering at his university. The experience made him start committing to object-oriented analysis and design. He is an author of power-assert-js. "97 Things Every Programmer Should Know" (supervised, 2010), "SQL anti-patterns" (2013, supervisor of translation). "Test Driven Development" (2017, as a translator) |
Takuto Wada
|
|
How I learned to stop worrying
and love record and playback
Abstract:
Record and playback tools like Selenium IDE have a stigma attached to them in our industry -- they're not worth your time, they produce tests that are impossible to maintain, and they're only for non-technical people. But with the new Selenium IDE, that's all just a bad rap. In this talk Dave Haeffner will squash the stigma by showing you examples of how Selenium IDE can reliably augment and level-up your testing practice regardless of your team's test automation maturity or your level of technical experience. He'll also share how he went from a record-and-playback naysayer to a Selenium IDE maintainer. Bio:
Dave is an active member of the Selenium community and a full-time maintainer of Selenium IDE. He is also author of Elemental Selenium (a free, once weekly tip newsletter on how to use Selenium like a pro) and The Selenium Guidebook (a guide on how to use Selenium successfully). |
Dave Haeffner
|
|
The future of Selenium - a Deep
Dive into the W3C WebDriver Specification
Abstract:
The WebDriver specification recently moved to W3C recommendation status and is already being supported by leading browsers and automation tools such as Selenium. This talk will take a look at it from the perspective of someone who has to implement a language binding or test-automation framework - using the WebDriver standard. In this session you will get to understand what exactly WebDriver is and how it enables automation of not just web-browsers but even desktop-applications. It will answer questions such as where WebDriver lies in the landscape of test-automation tools and frameworks. You will get to see live-demos and walkthroughs of code that uses the WebDriver protocol to achieve cross-browser test-automation. The architecture of a test-automation framework that uses WebDriver will be explained along with the different pieces such as the driver executable and how they all fit together. If you are interested in building test-automation frameworks, or better understanding what goes on under the hood - then this session is for you ! Bio:
Peter is a full-stack engineer who enjoys building and mentoring technology teams. An avid open-source enthusiast, Peter's first open-source project 'CB2XML' was created on SourceForge way back in 2004 and incredibly still sees active releases by the current maintainers. His latest open-source initiative is a web-services test-automation framework called 'Karate' - that has racked up 1400+ GitHub "stars" in less than two years. Peter also features in the TechBeacon list of "33 test automation leaders to follow in 2019". |
Peter Thomas
|
|
Journey of CI/CD Pipeline
Improvement in Yahoo! JAPAN
Abstract:
At Yahoo! JAPAN, each team had responsibility for their CI/CD system. They had problems with the cost of maintaining test pipelines and difficulties to share their CI/CD knowledge with other teams. Since 2013, they have worked to build a company-wide CI/CD system and maintain it. They also introduced automation test environment in order to enhance their development style. He will present the change.
Bio:
Teppei is an agile coach and software consultant. He has learned and worked to diffuse agile development and testing techniques/skills. He experienced them when he made things before. A chair of Software Test Automation Research Group Jp, An auditor of Agile Team Supporters, a keynote in JaSST'16 Hokkaido, translating "Fearless Change", etc |
Teppei Yamaguchi
|
|
Windows Browsers: How to Run
them in Docker containers
Abstract:
Microsoft Windows remains the most popular desktop operating system in the world with more than 80% of market share. Being so popular Windows is known to work unstable when running Selenium tests in parallel. While the mainstream Selenium approach is running browsers in isolated Docker containers - Windows browsers lacked such feature. This talk will first demonstrate how to run any Windows browser including Internet Explorer and Microsoft Edge in Docker container and to launch Selenium tests against it. Then I will show how to build a scalable Selenium infrastructure running Windows and Linux browsers on the same Linux machines with Selenoid project. Bio:
Having more than 10 years of Java and Golang programming experience. Maintaining large-scale Selenium infrastructure with thousands of browsers running in parallel during the last 5 years. Selenoid project core developer. |
Ivan Krutov
Developer at Aerokube
|
|
Technology supporting the
release of HOME'S
Abstract:
LIFULL HOME’S which was the name of a product changed to four times releases per week from twice releases per week by improving development processes. He would like to show two tips as below experienced then:
Bio:
Naoto joined to LIFULL as a new graduate. He is SETG through QC/QA role. |
Naoto Kishino
|
|
Testing in weekly
release
Abstract:
At Cookpad, they release recipe sharing mobile applications every week. He will explain what they do to accomplish the weekly release. He will also reveal their quality assurance flow in it. Bio:
Kyohei joined to Cookpad as a new graduate in 2018. His primary field is test-related activities. He got interested in test automation and quality improvement activities after experiencing product development as a mobile engineer. He is into Magic: The Gathering. |
Kyohei Kato
Software Engineer in Quality, Cookpad Inc.
|
|
Selenium at the Speed of
Headless
Abstract:
It’s no secret that testing is shifting left. Developers want instant feedback on the quality of their code, and testers want to incorporate tests earlier in the pipeline without slowing down development efforts. Testing in full browsers are great when you’re near the end of the pipeline and need to confirm full UI cross-browser compatibility. But they aren’t as effective for early pipeline testing, as they can slow down development and are expensive to maintain at scale. Enter headless browsers - an emerging solution that allows you to run your early pipeline Selenium tests at speeds you used to only dream of! By eliminating the need to test on full browser UIs at every stage of the development lifecycle, headless offers a lightweight option that gives developers faster feedback on the quality of code, all while decreasing the cost of maintaining testing infrastructure. Combined with a larger cross browser testing strategy, headless brings you one step closer to a true continuous testing solution that allows you deliver better quality software, faster. Join Sam Coffman, Product Manager at Sauce Labs, and Alissa Lydon, Product Marketing Manager at Sauce Labs, in a highly interactive session where they will discuss:
Alissa's
Bio:
Alissa Lydon is a Product Marketing Manager at Sauce Labs. During her four years at Sauce, she has worked with companies of all sizes in their journey to automation and continuous testing. From educating potential customers about the benefits of test automation, to organizing educational events for QA and development teams to learn more about industry best practices, her goal is to leverage her experiences with Sauce Labs’ customers to spread the word about how others can succeed with testing. Outside of work, you can find her cuddling with her dog, traveling to far away lands with her family, or catching a baseball game (Go A’s!). Samantha's
Bio:
Samantha Coffman is a Product Manager at Sauce Labs who manages the Virtual Desktop Cloud team, and is responsible for browser and OS updates as well as the introduction of a new Sauce Headless offering. Samantha joined Sauce a year ago and is energized about the direction in which desktop testing is heading! In the office, Sam loves to make charcuterie plates for her coworkers and play with all the office pups. Outside of work, you can find her traveling to a new city, exploring the food scene in the bay area, and spending time outside. |
Alissa Lydon
Product Marketing Manager at Sauce Labs
Samantha Coffman
Product Manager at Sauce Labs
|
|
What's that Smell? Tidying Up
Our Test Code
Abstract:
Given a smelly test automation code base which is littered with several bad coding practices, we will walk through each of the smells and discuss why it is considered a violation and demonstrate a cleaner approach by refactoring the test code live on stage. Bio:
Angie Jones is a Senior Developer Advocate who specializes in test automation strategies and techniques. She shares her wealth of knowledge by speaking and teaching at software conferences all over the world, as well as writing tutorials and blogs on angiejones.tech. As a Master Inventor, Angie is known for her innovative and out-of-the-box thinking style which has resulted in more than 25 patented inventions in the US and China. In her spare time, Angie volunteers with Black Girls Code to teach coding workshops to young girls in an effort to attract more women and minorities to tech. |
Angie Jones
|
|
Test Impact Analysis. Smarten
up your pipeline and reduce test time.
Abstract:
Are you struggling with the number of WebDriver tests you have? Do you run them continuously on every change? Have you tried all the things already been suggested? You run tests in batches, on multiple nodes, against light weight web application stripped of any animations? Well this is a presentation for you, as I was facing similar problem a while ago. Let me start with a bit strange question, have you ever considered generating test coverage report for your code, and either got discouraged by colleagues, or found out yourself, how uneasy to read and understand such report can be? What if I told you there is a hidden value in such report, and that this value is Test Impact Analysis. While test coverage can’t really tell you whether your tests are sufficient or not, it can tell you what tests are relevant for particular code, particular change. Automated tests are vital in guarding us from introducing regressions into our products. Tests aren’t just sugar and cream. They come with a cost. Execution time. Tests Impact Analysis determines how relevant tests are. Help you reduce execution time to minimum focusing only on the tests that matter. I will talk about our journey of adopting the technique in a product safety guarded by over 50k automated tests. I will share with you the challenges we faced and how we solved them. What kind of improvements we were hoping for and how we reduced execution time of all tests, including WebDriver by 30%. Also what we learnt from the experiment and what are our plans for the future. To summarise, I will show you how you can have Test Impact Analysis in your project using open source tools and what kind of strategy you’d follow to have it safely running in your pipeline. You will learn how we built our operational muscles as we were introducing Test Impact Analysis to pipeline, and how we treat all internal services affecting pipeline as production services, so that we can assure smooth delivery of critical fixes to our users. Bio:
Tester at heart. One could say, born to test. Keeping hands dirty with test automation and scripting since started professional career. Designing strategies, architecting, delivering frameworks and test environments for web and mobile applications. Actively involved in local testing communities. Presenting on most popular testing and development conferences in Poland and Europe. Since joined Spartez, helping developers at Atlassian become better testers. Teaching them how to explore. In love with big data, scientific method, and statistical analysis. In pursuit of quantifying quality in Software Development with a single formula. |
Bart Szulc
Quality Engineer
@BartSzulc |
|
Automating testing of automatic
measurement application
Abstract:
They would like to share problems and solutions they faced when they automated accuracy confirmation and functional tests against an auto measurement application. Yuichiro's
Bio:
Yuichiro is in a quality control engineering team at ZOZO technologies. He is a programmer expertise Java, Swift and Python. He focuses on test automation as a QA engineer role. |
Yuichiro Endo
Quality
Assurance Engineer at ZOZO Technologies, Inc.
@ochacha_ui |
|
Client Side Speech Recognition
Testing
Abstract:
With many of today's applications accepting voice input or integrating with speech recognition engines from Google, Amazon, Apple, etc., it's imperative that QA teams are able to test speech input within their applications. Using Docker-Selenium images and PulseAudio, Rosetta Stone’s QA team has created a Docker image that allows pre-recorded audio files to be passed in to a simulated microphone, as if a user is speaking the audio. This talk will take a look at some of the available alternatives we explored and their limitations, how we integrate PulseAudio into the Docker-Selenium images, and how we play our audio files within our Selenium tests.
Bio:
Paul has been in the QA industry for over 7 years. He is currently a Lead Quality Engineer at Rosetta Stone, focused on tackling larger QA initiatives such as in-house mobile CI testing and automating speech recognition. He is an open-source enthusiast and has contributed code to Appium Desktop, TestArmada's Nightwatch-Extra, and other open-source QA tools. |
Paul Schroeder
Lead Quality Engineer at Rosetta Stone
@pschroeder89 |
|
Toolbox for Selenium Tests in
Java: WebDriverManager and Selenium-Jupiter
Abstract:
This talk presents two open source tools designed to simplify the use of Selenium from Java code. On the one hand, WebDriverManager allows to automate the management of the required binaries by Selenium WebDriver, such as chromedriver for Chrome or geckodriver for Firefox. On the other hand, Selenium-Jupiter is an extension for JUnit 5 which allows to control local, remote or “dockerized” browsers and Android devices in seamless way. This extension offers a rich variety of features, including remote access with VNC, session recording, test templates, or integration with Jenkins. Bio:
Boni García is an Assistant Professor at Universidad Rey Juan Carlos in Spain. He is passionate about software testing, web engineering, and open source. He is the author of more than 30 publications including international conferences papers, journals, and the book “Mastering Software Testing with JUnit 5”. He is the creator of different open source utilities for Selenium, including Selenium-Jupiter (a JUnit 5 extension for Selenium) and WebDriverManager (a well-known helper library aimed to automate the management of binary drivers for Selenium WebDriver). |
Boni Garcia
|
|
The edge of the pyramid
Abstract:
How long does your build take? Hours? How many times does your build go red, but no one seems to have broken it? You know it, this build smells, but how you can improve your build and keep it green? It’s easy, Just move the touchy tests to the bottom of the testing pyramid. Join me on this quest! Bio:
After three years working as software developer, Elena decided to change its career and focus on quality. She discovered techniques as BDD and realised how important is quality inside of the development process. She accepted a job as software engineer in test at Roche Diagnostics, Barcelona. After spending a couple of years at Roche She joined Netsuite-Oracle. In Netsuite, she realised that if we want to create good quality apps, the whole team should be involved in testing. For this reason, she started to do talks, workshops, pair testing sharing its passion in testing with its coworkers. After three years, Elena decided to take one year unpaid leave and discover Japan. Seems like one year is not enough, so she decided to stay. Nowadays is working at Electronic Arts as Quality Analyst, sharing its ideas in this part of the world. |
Elena Alejo Teissiere
Software Engineer in Test
@elenapinkywinky |
|
Collaborating on Open Source
Software: How I Started contributing to Open Source and Why
You Should Too
Abstract:
There are several reasons you might want to contribute to open source software. For me, it was that I wanted to learn in a more useful way than doing programming challenges. So I looked into how I could contribute to open source projects that I use myself. After contributing for almost two years, I notice that I have learned a lot from my contributions (which has been useful at work), as well as have made friends and have become part of a community. In this talk I will share my experience with contributing to Cucumber, including an early mistake (merging something that wasn’t ready yet) and fixing it with the support of core contributors, and still feeling welcome! You’ll learn how how to find your project and contributions to start with, how to connect with the community to make sure your contributions are useful and the many types of contributions you can make. Contributing to open source is a way of paying back to the community. In addition, it is a way for you to learn, collaborate and become part of a community. Getting (constructive) feedback on a pull request and collaborating to make things even better is a great feeling! Bio:
Marit van Dijk has over 15 years of experience in software development in different roles and companies. She loves building awesome software with amazing people, and is an open source contributor to Cucumber. She enjoys learning new things, as well as sharing knowledge on test automation, Cucumber/BDD and software engineering and blogs at https://medium.com/@mlvandijk. Marit is currently employed at bol.com. |
Marit van Dijk
|
|
Make your automation work for
you
Abstract:
For a number of test and quality engineers, the automated tests that are created are automated versions of manual tests and workflows. Nothing fancy about them. Nothing that improves the quality or lowers the risk of defects within the test suite itself. They run faster, but that is the only benefit. Doing that creates a static regression test suite. In this day and age test engineers should be able to write tests that hit the edge cases without writing them out. Tests are written this way provide more value every time they run, and can solve for a few important use cases: How do you deal with your mobile apps or different screen resolutions? Do you write out tests for these options? If you do write out those cases individually, how much time do you spend doing so? How do you deal with dynamic data for your tests? How do you reproduce a test with specific data? Even harder still is sharing specific test cases that fail with team members. How do you go about sharing those details? Bio:
Andrew Krug found his calling early on in his career -- test automation. Where he rightfully earned his nickname "The Lazy Coder." During his journey, he has built test automation infrastructures at scale for both desktop browsers and mobile devices. In his spare time, he is a Selenium Co nference Committee Member and runs the workshop Diving into Selenium at all of the Selenium Conferences. Andrew is now currently consulting about quality engineering and software development practices at Gingham Consulting and blogs at LazyCoder.io. |
Andrew Krug
|
|
All is thanks to you,
Selenium.
Abstract:
Selenium, which is a well-known automation tool in all of the world. This talk is for you who are hesitating to introduce it in your project. He will show brilliant tips about the Selenium so that it makes you want to resolve tasks using it. Bio:
Kim is a primary engineer in Rakuten ranking test automation team. He was a leader in Korea Army. He has an enthusiasm to build a rapid development environment avoiding risks taking advantage of the army experience. He is a romantic guy since he has been going out for eight years with a first love Japanese lady. |
Kim Woohyeok
Software
Engineer at Rakuten, Inc.
site |
|
Blockchain 101 - Growth &
Pains of a Tester
Abstract:
Have you ever found yourself at the start of a new project wondering how you're ever going to understand the technology? How would you even begin to test that? That situation was where Kim found herself earlier on in 2018 when it was decided by the business to build a product that would be using blockchain technology. The product would allow users to purchase gold and silver backed cryptocurrency. Join Kim as a confessed newcomer of both blockchain and automation engineering the experiences of bringing such a product to market including the steep learning curve she had to ascend. We will go on a journey starting with an overview of blockchain technology. During this time commonly used terminology in association with blockchain will be explained. Highlights will include some of our team's lessons learned during development. How the diversity of our team assisted in a well-rounded associated product and the identification of early pains that molded the UI & UX. Kim will share the teams current methodologies and test strategy including innovative ways to test that were embraced during development. Finishing with a live demonstration of creating a transaction and verifying its been added to the blockchain. Bio:
Kim Nepata comes with five years of overall testing experience in various roles including blockchain and finance. Kim is rich in life experiences and professional diversity, due to her varied career pathways which have included sales, advertising, and insurance underwriting. As a newcomer to this industry, Kim finds herself continually pushing the boundaries in her professional growth based on the strong intent of always developing quality user-friendly software. She is active on tester forums, co-founder of Lean Unwind Meetup Brisbane, and is a reflective blog writer about her own testing experiences. |
Kim Nepata
|
|
Testing for an Inclusive Web:
Accessibility Testing
Abstract:
One billion people are estimated by the World Health Organisation to have a disability. W3C's Web Content Accessibility Guidelines (WCAG) are becoming increasingly mandated by governments and are being used by many industries to make websites more accessible for people with disabilities. Developers are often told to make their websites accessible like it is an easy light switch you turn on or off but, it is not easy. Manoj will explain about ways you can test for Accessibility manually and also ways you can save time with automated accessibility testing and need for it and show us how it can be added to our existing automation suite using tools like Selenium with no or minimal effort. Most companies are moving into Continuous Delivery and DevOps model, with quick delivery cycle with an enablement of Continuous Integration tools, to match this speed a fast feedback mechanism Continuous testing - "Automated testing" is used to validate the build, but why just functionally validate, lets also validate the accessibility of app to check if it can be accessible by everyone that include people with impairments/disabilities and cater to that 20 % (1 billionth) of population who are with some impairments. This session will help you understand: What is Accessibility testing What are different tools available to automate accessibility testing Do we need separate efforts to automate accessibility testing Do we need expertise on accessibility Bio:
Manoj is a Technical Lead at Applitools, a Selenium committer and a member of the project leadership committee. He is an open-source enthusiast and has contributed to different libraries that shall help test the apps better with libraries like Selenium, ngWebDriver, Serenity and Protractor. He is also the author of a Selenium blog AssertSelenium and an Accessibility enthusiast. |
Manoj Kumar
|
Sponsor
Session
|
Development platform for Mobile App in Yahoo Japan Corporation
Abstract:
Yahoo Japan provides over 100 services and develops many mobile apps. Our team develops and maintains CI/CD tools that make efficient to develop various services. In this session, I will introduce what tools we are developing in our company and how to use Appium and other OSS to efficiently conduct tests, builds, dog fooding and feedback. Bio:
Hiroshi Nishijima is a developer at Yahoo Japan Corporation who develops the test platform for mobile applications. He has over 10 years of front-end development experience, and he is interested in improving development process. |
Hiroshi Nishijima
Developer at
Yahoo Japan Corporation
|
Sponsor
Session
|
How to realize a large-scale Appium server with Remote TestKit
Abstract:
Remote TestKit is a device cloud service which provides a large number of mobile devices released in Japan and other countries/regions. In addition to manual testing, automated testing can also be available, and the Appium server is provided as one of the automated testing features. This session addresses how to realize an Appium server with over 500 mobile devices on Remote TestKit. Bio:
Koji Hisano was the founder of Katomakku Inc. which provided a device cloud service. The company was acquired by NTT Resonant Inc. He continue to develop the service: Remote TestKit. |
Koji Hisano
|
Sponsor
Session
|
How
Selenium and Appium support LINE services
Abstract:
LINE Corporation provides multiple types of services to the world in addition to the LINE app. Automated tests have become a must for the fast development and release of functions nowadays. In fact, LINE conducts a variety of tests in various phases, including development and monitoring. Among them, the E2E test is one of the most important since it is conducted in a situation close to users and, that is where Selenium/Appium are playing big roles. I'll be speaking about what LINE does to leverage Selenium/Appium. Bio:
Automated Test Team Manager, Development Dept 2, LINE Fukuoka Corporation Mainly in charge of developing systems and libraries related to automated tests. |
Hiroaki Ozono
|
Sponsor
Session
|
The Operation of Automated Tests
Abstract:
Humancrest has been performed automated E2E tests on a variety of customer services. We have developed and operated Lynx as a platform for automated testing. Starting an automated test is no longer difficult. However, UI testing is slow and fragile, so it is difficult to maintain and operate. I think automated testing of E2E makes sense when it became continuable. I would like to introduce you how we are working. Bio:
Experienced almost all occupations (requirements, developments and operations) for 20 years in various companies. After experiencing above all, recognized that quality is the most important matter for the industry, and so joined QA business. E2E testing and performance / load testing are my favorites. |
Tomotaka Asagi
|