Speakers & Talks
The 2020 is not a time to focus on Jenkins configuration and yet another wrapper for Selenium. 2020 is time for the next step. Augmenting tools in test automation, powered by ML. delivery pipelines extended by Security Testing, Security information and event management (SIEM), Serverless approaches in automation, and flexible Multi-cloud infrastructures. DevOps, TestOps and DevTestSecOps is our inspiration for the talks.
27 out of 32
So, last year we figured out that no one is getting fired. Phew, that’s good. But we also figured that if your business is not transforming, it will fall behind and become irrelevant. That’s bad. So, what can we do?
In the talk Baruch will explain what to learn, what to say, and what to do when the argument “this is how they do it in Netflix” doesn’t work. We’ll discuss the required reading list, who to talk to (who are those mythical “stakeholders” and why are they holding those steaks? Is it a meat factory transformation thing?), and what to say: how to go about digital transformation for the sake of the future of the business in general, and the testers in particular.
About Baruch Sadogursky 🎩
Baruch Sadogursky (a.k.a JBaruch) is the Head of DevOps Advocacy and a Developer Advocate at JFrog. His passion is speaking about technology. Well, speaking in general, but doing it about technology makes him look smart, and 19 years of hi-tech experience sure helps. When he’s not on stage (or on a plane to get there), he learns about technology, people and how they work, or more precisely, don’t work together.
He is a CNCF ambassador, Developer Champion, and a passionate conference speaker on DevOps, DevSecOps, digital transformation, containers and cloud-native, artifact management and other topics, and is a regular at the industry’s most prestigious events including DockerCon, Devoxx, DevOps Days, OSCON, Qcon, JavaOne and many others. You can see some of his talks at jfrog.com/shownotes
JFrog, Developer Advocate
Once the infrastructure is designed you should be able to deploy it effortlessly. This has long been the goal and can now become a reality!
Cloud solution architects and DevOps engineers want to have a faster conversion from idea to product. They don’t necessarily care about the foundation on which it runs. It’s supposed to work and provide the functionality specified. So how do you go about making that happen?
What if there would be a way to draw an architecture online and get the infrastructure for it implemented as code automatically?
During the talk, I will demo how it is possible to create AWS architectural diagram in the browser and get it converted to working Terraform configurations and show it all in action.
This talk will be rather interactive and involve the audience, as I will be asking for inputs and base the demo on them.
About Anton Babenko
Anton Babenko is AWS Community Hero and helps companies around the globe to build solutions using AWS and specializing in infrastructure as code. Build DevOps and reusable infrastructure components.
Anton spends a large amount of his time as an open-source contributor on various Terraform & AWS projects. He enjoys solving real cloud architecture tasks, and above all, makes them Open-Source.
His most successful projects are:
- the collection of Terraform AWS modules (terraform-aws-modules on GitHub), in fact, downloaded more than 4 million times,
- EBook describing Terraform best practices established in the community (www.terraform-best-practices.com)
- modules.tf which converts visual diagrams to infrastructure as code in automatic way
Anton Babenko co-founded and co-organizes AWS, DevOps, HashiCorp User Groups in Norway, DevOpsDays Oslo, and, in addition, often speaks at various technical meetups and conferences.
Happy to visit DelEx Conference in Minsk with arrival from Oslo
modules.tf, Terraform AWS fanatic
The words ‘artificial intelligence’ are widely used these days. However, courses on AI usually are quite boring. What about a crash course using the most popular game of the year? Even if it might seem as a ‘game for children’, Minecraft AI bots are currently being used for research by big, serious companies, besides all level students.
This kick start session on Minecraft automation and AI does not require you to have any prior knowledge, but if you have it, all the more fun! It also does not require you to have played the game (but I cannot guarantee you would not like to play it afterwards)
We will get to know how to write programs with Minecraft using a mod called ComputerCraft and see a demo for it.
Then, we will learn about another mod, AIX, that allows you to program AI bots. We will see another demo of it functioning while understanding some basic AI concepts.
Finally, we will discuss applications, current researches and funny stories.
About Noemi Ferrera
Noemi Ferrera is a computer scientist passionate about technology and testing.
Noemi holds the position of senior software developer in test and she strives for quality, automation and tooling creation to ease the entire development process. Her career goal is to research new technologies (such AI and VR) and apply them into testing.
Noemi Ferrera has worked in multinational companies such as IBM, Microsoft and Dell and also in a startup in Ireland.
She was working in China for a while, to work at Netease Games, where had a chance to gain expertise in Image Recognition and visual-based testing.
Now Noemi works in SauceLabs company.
Sauce Labs, Solutions architect
This talk will look at some challenges we face during testing and automating features like location based features, bandwidth simulation, network interception etc with Selenium WebDriver and how that can be solved with DevTools, and in particular, Chrome DevTools.
Chrome DevTools is one of the most useful web developer tools. It allows you to get comprehensive information about the page and requests and emulate mobile browsers on slow devices.
Some of the blockers which we faced with Webdriver was to automate:
- Getting events from browser like when specific network call completed
- Setting the fake geo-location from your WebDriver scripts
- Updating the user-agent
- Mocking the web response by intercepting the traffic
- Simulating network bandwidth especially for Mobile Chrome
As our team had built a good number of a test cases with user-journeys it was hard for us to move out of Webdriver and rewrite all our tests. So we decided to take the advantage of chrome dev tools API which uses web socket communication and implements our selenium web driver test to access all the API.
An outcome of Session:
A demo about how you can use the power of DevTools in Selenium tests and how to make the debugging more convenient.
About Fathima Harris
Fathima Harris is a Senior Quality Analyst working at ThoughtWorks.
Fathima has been working primarily in the retail domain and has about five years of experience. Fathima’s expertise lies in functional testing and performance testing. She enjoys spending her time looking at various challenges in the project delivery cycle and finding different ways to solve them.
Fathima is also a security Enthusiast. And volunteer in organizing local events, related to test automation practices. Lived and studied in Kuwait for 5 years
ThoughtWorks, Senior Consultant
With this talk Dmitry will share the thorny path of an infrastructure migration in the Flo Health company from a hardware to a cloud, from zero to hero. Epic path consisted from 2 path and not a trivial approaches to migrate 6TB of data.
Newly designed approach and model, metrics issues and solutions. How positively or not it affected pipelines, terraform for developer, etc. And what the confrontation between push and pull strategies led to. Which is quicker? We know, since have metrics for this as well.
About Dmitry Yackevich
DevOps enabler (and sometimes disabler) at Flo, PandaDoc, Targetprocess and Workfusion.
At work he mostly solves problems created by himself.
Flo Health Inc., Infrastructure Lead
Our lessons-learned story after we met with Account Security Assessment. The story of Security Information and Event Management enrolment, which was applied for continuous monitoring be means of AWS services such as GuardDuty and Macie, OpsGenie and Security Hub.
This this talk Roman will share the first steps from scratch, implementation approach and cost comparative analysis. Results and next planned steps.
About Roman Zelenko
Roman Zelenko is a Security lead and savvy. In fact, participated in improvement and development of demand cloud and application security technologies.
Flo Health Inc., Lead Security System Engineer
Selectors in Automated UI is a pain point: tests sooner or later “breaks” due to changes in layout. Which makes UI tests unreliable as a part of testing pipeline and Continuous Testing itself. Layout mutate and as a result test crashes, builds turn “red”.
In this talk Anna will give a word regarding easiest way how to hack this problem in the bud. You will learn about the newly open-sourced tool for self-healing automation called Healenium.
Healenium allows to overcome problem of instability of automation tests automatically and spend less time supporting tests. Now it works for 📱Mobile Automation as well !
About Anna Chernyshova
An expert in the field of BDD, an adherent of engineering and DevOps practices.
Anna has strong experience in test automation frameworks development and building of test automation approaches and processes. One of the creators of the BDD library Akita.
EPAM, Lead Software Test Automation Engineer
Modern software development methodologies and approaches help to increase delivery speed while still caring about software quality. However, if we think about manual regression tests, they are not only time consuming and repeatable, but also feedback time is quite high. These are the reasons why regression tests are often automated.
Automated tests can provide results faster and it’s possible to execute them more frequently than manual ones. They can decrease the overall time needed for tests, but what’s probably even more important, they allow to test and receive feedback earlier in the development process. It’s essential if we want to release and deliver business value faster and more frequently.
But what if we have more and more tests and even automated execution of them takes too much time – 10 minutes… 30 minutes… maybe even hours? Should we consider the ability to execute full tests set just a few times a day as something normal? Or maybe there are too many high-level tests? Is adding more compute resources the only option to reduce the execution time?
During the presentation, you will see how the serverless cloud services like AWS Lambda may be used to run tests in the highly parallelized environment that can speed up test execution even hundreds of times.
About Tomasz Konieczny
Tomasz Konieczny is a senior QA Engineer at Ro. Tomasz is specializing in test automation but is also interested in a wide range of QA related subjects – from test architecture to server setups.
Tomasz is a DevTestOps evangelist and automation enthusiast. He spoke at multiple conferences mainly related to software quality like TestCon Moscow, Testing Stage, What The H@ck, Testing United, Devoxx Poland, 4Developers, TestWarez (four times), Warsaw IT Days, TestCamp, TestFest, ConSelenium (twice), PyCode and Quality Excites.
Ro, Senior QA Engineer
“The Linux Audit daemon is responsible for writing audit records to the disk, which you can then access with ausearch and aureport. However, it turned out that parsing and centralizing these records is not as easy as you would hope. Elastic’s new Auditbeat fixes this by keeping the original configuration, but ships them to a centralized location where you can easily visualize all events. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
This talk shows you what can you do to discover changes, events, and potential security breaches as soon as possible on interactive dashboards. Additionally, we are combining Auditd events with logs, which are security relevant, and explore them in Elastic’s free SIEM.
About Philipp Krenn
Philipp Krenn lives to demo interesting technology. Having worked as a web, infrastructure, and database engineer for more than ten years.
Philipp is now working as a developer advocate at Elastic — the company behind the open source Elastic Stack consisting of Elasticsearch, Kibana, Beats and Logstash.
Philipp based in Vienna, Austria, he is constantly traveling Europe and beyond to speak and discuss about open source software, search, databases, infrastructure, and security.
Elastic, Developer Advocate
In this talk Artem will make a deep dive into the dynamic provisioning of GlusterFS volumes in kubernetes with Heketi. With overview of mentioned stack and detailed description of solution architecture, build on top of mentioned stack.
Be ready to look into the source code with Artem, and see how Heketi works with GlusterFS. Is it issue-free? Nope for sure. So Artem will go through most common troubleshooting. Describe possible improvements and develop it from the ground-up.
The outcome of the talk: common mistakes in the architecture, conclusions and recommendations.
About Artem Romanchik
Artem has over 8 years of experience in Windows and Linux environments, focusing on the areas of Cloud Computing and open-source virtualization technologies. At the same time Artem advancing his skills in hardware planning and maintenance, capacity planning, troubleshooting and performance tuning.
Also he has experience with blade&server platforms of different vendors (SuperMicro, Huawei, ZTE) and variety of Unified Messaging technologies.
Last years mostly in Microsoft Azure (Web, Networking, Powershell, Compute, Storage, etc).
Targetprocess, Inc, Systems Engineer
With this talk Sergey wants to re-think the nature of test coverage, based on project based experience.
Sergey will explain why it’s important to know the magic number 42, and why we misunderstand it. The talk will address capabilities of Test-to-Code mapping which is a cornerstone of Test Impact Analytics and source of data for Test Gap Analysis.
Sergey plans to unveil new tool, which can augment daily activities in testing, and highlight ideas that will help QA engineers to succeed in their testing efforts.
About Sergey Pirogov
Winner of Ukraine IT Award 2018 “Quality Assurance”. Test automation enthusiast and blogger, podcaster aims to advance automation practices via popularization of knowledge at related technologies.
Contributes to community as an active speaker and program committee member.
Founder of automation-remarks.com and QAGuild Podcast and QAGuild community.
EPAM Systems, Solution Architect
“Selenoid is a powerful implementation of Selenium hub using Docker containers to launch browsers” it describes itself. It’s open source and free. An in particular, it has an enterprise version named “Moon“.
This particular talk is a 45 minutes master class.
Being a mainstream and widely used browser automation tool Selenium protocol lacks many important features: network requests analysis, application performance profiling, accessibility tree access and many more. This is why we are seeing more and more conference talks about so called Chrome Developer Tools protocol where all these features are already present. This protocol is already supported in Selenoid – an extremely efficient Selenium solution running browsers in isolated Docker containers. This talk is a live demonstration of what is Chrome Developer Tools, what you can already do with it and how to use while running parallel Selenium tests in Selenoid.
About Ivan Krutov
Developing in Java and Golang for more than 10 years. Have been working on the creation and operation of high-load Selenium infrastructure for the last 5 years. Support round-the-clock operation of the Selenium cluster of more than 5,000 parallel browsers.
One of the main developers of the Selenoid project and related tools.
This talk will describe pros and cons of architecting Hybrid cloud and multi cloud environments. Possible complications of processes from DevOps prospective.
Multi-cloud infrastructure is also the way to avoid Vendor Lock, but it brings own aspects in context of hybrid/multi cloud solutions.
About Nikalai Stakanov
System Architect DevOps, CI/CD processes development speedup and improvement Public, private, hybrid clouds and cloud and various cloud technologies. Has a 10+ years experience in System engineering.
EPAM, Systems Architect
With this talk Ivan will address Big Data related infrastructure in Flo. Ivan will tell you a little about what data they have, how much of it, and what they do with it and what are the plans going forward.
- Building a data lake in AWS: where to start, how to receive data, where to store it, and where to store it.
- Organizing a data catalog using AWS Glue. How we use Glue in Flo and what features of the service can be useful.
- The organization of data processing: AWS EMR for the win!
- DWH and Analytics: Aurora, Redshift, Athena and all-all-all. Which tool to choose for analysis and how not to make a mistake.
- Lessons: how to fill cones
- What else: a quick overview of other available services and tools for storing, organizing, and working with data available in AWS.
- First results with Presto: performance improvement, scaling
About Ivan Sharamet
Ivan Sharamet is a passionate software engineer with 10+ years of experience building things for various industries (healthcare, travel, semiconductor manufacturing). Google Cloud Certified Data Engineer.
At the moment, Ivan works on building applications for Big Data processing and analysis using tools like Scala, Apache Spark, Kafka, etc.
Quite familiar with major cloud providers (AWS, GCP and Azure) Big Data tools.
Flo Health Inc., Software Engineer
In this talk Alexei will show testing that goes beyond your daily work with the software. Insights into to Continuous Testing and CI/CD process in robots development, which stands on the edge of hardware and software testing.
You will learn about robot testing. Chosen strategy, what thorny path they have passed and what was the starting point.
Considered approaches to testing at different levels and for different parts of the system. What tools were used, how we came to them and what was the basis for their choice.
About Alexey Boole
Charismatic and charming speaker, heading QA practice in Rozum Robotics.
Prior to it, Alexey was a Engineer in Test at JUNO, RnD department in Minsk location, and Alexey recalls these times of working in Juno startup with great warmth to the team and professionals with whom he had a chance to work.
Before joining JUNO, Alexey served QA Automation Engineer in Wargaming, that was a time when Alexey started to speak at conferences.
Once upon a time, Alexey worked as a programmer on the Belarusian railway. But the prospects for growth and wages did not please him. So he moved to Synesis as a tester.
Rozum Robotics, Head of QA
Puppeteer by Google Chrome takes the world of browser automation. But can we use it for testing?
Sure! What features contain Puppeteer, why it’s better than WebDriver, and how it drives your tests faster?
Let’s take a look of features of Puppeteer, as well of common testing patterns in it. We will look also work on problems happening during Puppeteer testing and simple tricks to resolve them.
Even you already work with Puppeteer, this talk will be valuable to you!
About Michael Bodnarchuk
Michael is web developer from Kyiv, Ukraine, who is passionate in automating testing.
You may know his projects: Codeception (PHP testing framework) or CodeceptJS. Michael is tech consultant and trainer in SDCLabs, where he helps companies build better test automation for their projects.
Amazon Web Services (AWS) offers a huge and ever-growing number of services that can take weeks or months to get familiar with, and during that time, new ones will appear.
In order not to drown in this ocean of possibilities, it is necessary to highlight those that are offered for the implementation of CI/CD processes. Let’s look at how AWS saws CI/CD itself, what it uses for this and what it offers for integration with other solutions.
Continuous Integrations – consider AWS Code * services and their capabilities for developers, testers, and developers.
Continuous Delivery – divide a wide range of infrastructure services from AWS Elastic Beanstalk to Amazon EKS by simplicity-complexity, capabilities-cost and choose the right one.
As a result, you can confidently navigate among the AWS services that are applicable to CI/CD, and choose the most suitable options for yourself.
About Roman Sevko
Roman Sevko, as an owner of one well known channels AWS Notes, works as a AWS DevOps Consultant, starting 2012. Despite on fact that he is located in Minsk, Roman works as independent consultant with big logos around the globe.
Amazon Web Services started for Roman from early 2012. He builds CI/CD processes both in the code and as a whole for the organization scale. Adheres to and preaches the principles of efficiency, security, Infrastructure As a Code, Immutable Architecture and other Best Practices.
Roman also participates in educational projects for training and retraining AWS specialists.
Safe Frontier, AWS DevOps Consultant
The best defense against unexpected failures is to build resilient services. Testing for resiliency enables teams to discover these failures before the customer notices. In my talk I’m going to present open source tool that can be used for containers resilience testing, stress testing, and network emulation, running on a Docker host or on a Kubernetes cluster.
About Alexei Ledenev
Alexei Ledenev is a Cloud Architect with experience over 20+ years, in positions as Senior Architecture/Technology positions.
In fact, Alexei contributes into the practice of DevOps, Software and Test Automation with his own 9 patents.
Alexei says “laziness is the engine of progress” and automates everything!
He knows how to achieve 100% CI/CD automation, being passioned about right architecture, code quality and automation – “test is the ultimate proof that code is working” Alexei Says.
Alexei contribute to practice by maintaining open source projects, publishing Medium blog posts and speaking at the conferences and meetups.
Self-directed learner; my current favorite technology stack: #Go, #Docker, #Ansible, #AWS, #Python, Machine Learning
Consultant, Cloud Architect
Today it’s impossible to imagine companies that would not use CI/CD. One of the main components of which is testing. At the early stages of business, test execution time is comparable with the other pipeline components, then with the project growing it increases significantly both in terms of execution time and price. In our presentation, we will show you our experience in building an infrastructure for test automation using Terraform. The main goals of the infrastructure would be scalability, easy support, simple deployment and configuration. Since you need to work not only with cloud providers but also with real computers, Terraform has become an ideal solution in this case. As a result, we got an infrastructure that is practically independent of the technology for writing tests, it is easily integrated into the process and it has an extremely low cost of running tests.
- Automation testing in perspective of CI/CD pipelines
- How painful to build the automation infra from scratch
- Terraform as cluster-agnostic infra builder
- Profit we experienced from Terraform usage
About Andrew Nazarenko
Andrew organized and leading internal tech talks in Solvd company. Have organized and leading test automation courses for Solvd employees in Belarus, Ukraine and Argentina.
Solvd., Test Automation Architect/Head of Automation Department
72 months in live with Zero tests: a true story about building continuous testing on a project in live from scratch
The talk is neither about building test automation nor about frameworks or approaches. It is about difficulties one can face introducing brand new activity in the company after 6 years of successful live operation. In such circumstances, it’s natural for a person to have more questions than answers:
- What to test first?
- Where to get the requirements?
- Who is responsible for production issues?
- How not to slow down the delivery?
- Is testing documentation really needed?
Elena will share her experience of finding answers to these and other questions when bringing continuous testing on a live project.
About Elena Kulgavaya
Helps people to get addicted to the programming. Accuracy and precision obsessed engineer. Believes her main role is to make the live easier for everyone.
Lyte.com, QA Lead
In this this talks presentation Yaroslav sharing his experience on how to build an effective Alert Management system for a large and complex distributed system.
It will disclose tips and practices on how to protect it from uncontrolled changes in used SaaS solutions.
Yaroslav will share his experience of how to clean the system of annoying noise. How to build clear rules for prioritization and escalation.
And spice up this with examples of how to distinguish a good alert from a bad one and explain what is a good alert.
About Yaroslav Budyansky
Yaroslav Budyansky has more than 10 years in the IT industry, 6 of which Yaroslav works in Wargaming Company.
In fact, Yaroslav started DevOps when it wasn’t a trend. Thanks to his experience in development, operation and entrepreneurship, Yaroslav knows what each of the parties needs.
By chance, knows how to “sit on two chairs“.
Wargaming.net, DevOps TeamLead
GitOps has been around for several years already. In fact, it’s not that neoteric, since it’s mostly good old Infrastructure-As-A-Code and Configuration-As-A-Code principles being applied to microservices/cloud-native/k8s world. Pretty simple, isn’t’ it? But, there’s always a “but”.
This talk will cover our experience with building Continuous Delivery via GitOps here, at TargetProcess. We’ve been using this approach in production for some 3 years already, being able to (more or less) successfully manage umpteen microservices in dozens of production environments. Our stack is terraform, docker, k8s, helm, nexus, git(lab) and friends (where “friends” stands for our internal developed set of tools that puts all the pieces together).
We’ll start with a brief introduction to GitOps itself, it’s history and main concepts. Then we’re going to recollect our own experience with GitOps: the background, architectural decisions, technical stack, custom development, pitfalls, wins and failures – everything that we’ve faced during recent years. Finally we will address the global picture of GitOps (well, at least the part of the picture that we suppose to see).
About Illya Dus
Illya Dus started his career as a Cybersecurity Engineer and Cryptographer and later shifted to Software Developer role.
He worked on a projects of different scale and culture, from small startups to big high-load products with teams distributed across the world.
Illya is always passionate about efficiency, predictability and things-under-the-hood, so it was natural for him to move to Targetprocess Inc, where he’s a part of Infrastructure Development team.
Illya has a rather wide set of interests, including but not limited to: software engineering, cloud-native platforms, cybersecurity, cryptography, devops, sports (football mostly).
Targetprocess, Inc., Infrastructure developer
Modern methods for coverage measuring are good only for development. However, the amount of useful information from coverage reports is extremely small. One the one hand all code lines weren’t involved during tests. On the other hand, the only important information is the percentage of coverage. And we are not interested in the absolute value, but we want a delta with the previous one. Artem will present some simple solutions that allow you to evaluate the coverage of tests written by test automation.
API tests. There is a swagger and during his execution, we also collect a swagger. We count coverage as a diff of two swaggers. We can see what is covered, what is not and what data.
Web tests. During the execution of tests, we collect information about elements, pages and actions. As a result, we have such format: a. page; b. elements; c. actions; d. tests.
All this is sent to the plugin. We draw elements on the page that were affected during these tests. Plus additional information: the list of tests on the video page.
As a result, we can answer the next questions very quick:
- What is covered and what isn’t
- How it was covered (just clicked or checked the text)
- What tests go through the page
- Which elements are most commonly used? In general, we should avoid it because it’s a potential point of failure.
- Point to the test, see the Selenoid video.
- Connected to Selenium. It can be easily completed for the puppeteer and for anything else. It will be convenient to understand what is being checked and why.
About Artem Eroshenko
Artem Eroshenko works in web app testing automation for more than 8 years. Has worked in different teams and occupied different positions up to the head of automation testing group. Has a vast experience with popular tools (Selenium, HtmlElements, Allure, Jenkins). Codes mostly in Java and Groovy.
Consultant at QAmeta.io
About Dzmitry Prakapuk
Dzmitry Prakapuk has more than 7 years experience in automation testing. Dzmitry worked on different roles like QA Architect and Test Automation Lead. Has experience in delivering backend and frontend separately. Works mostly with JS tools (Jest, Puppeteer, Cypress, Protractor, WebdriverIO, CodeceptJS)
EPAM Systems, Lead Software Test Automation Engineer
From the talk you will know which sacrifices sometimes you have to do to achieve stability.
Aliaksandr will share his vision about metrics that can be useful for everyone, regardless of the used platform.
Attendee will learn how Oxagile continuously rotate credentials in AWS for services and users.
And finally when they are going to migrate to k8s.
About Aliaksandr Karavai
Aliaksandr has more that 6 years experience in engineering and more than 3 years in DevOps.
Нe learned from the best and is fully committed to Cloud technologies and fond of analyzing success and attempts to measure it.
Aliaksandr suppose that there are no limits to perfection but you always need to soberly evaluate the outcome from each iteration.
Also Aliaksandr shares duties with team on CI/CD Slack driven workflow based on Jenkins, Application Gateway(CodeBuild, CodePipeline). Use Nomad as container orchestration and complementary Hashi tools (Consul, Vault) to manage micro-services platform based on Docker containers.
Oxagile, DevOps Engineer
SDET stands for Software Development Engineer in Test or Software Design Engineer in Test, this kind of role is originated from Microsoft and currently many organizations are demanding such SDET professionals who can participate in development of the application and also in testing of the software developed.
But do companies get this title right? Or just sell same people to the clients with a new price tag above new title?
Is it a new engineering line to advocate clients and product quality or just a rattle-title for engineers instead of promotion?
This is a discussion of a group of people representing companies, handzone experts, staffing, raise pressing questions about SDET title.
About BOF discussion
BoF (birds of a feather) an informal discussion group. Unlike special interest groups or working groups, BoFs are informal.
An open discussion of experts and not accidentally random participants around a given often very acute and hot topic.
Very often the projects that have already gained the course and have a large codebase conclude that you need to write autotests. Including the UI autotests. In this situation, you don’t have the opportunity to remake the architecture for tests. As a result, tests became unstable and distract the product development team more than they help it.
In his talk Andrey will tell:
- how to lower the threshold to project participants tests;
- how to build simple and clear UI autotests architecture;
- how to make tests stable without changing application architecture and how to deal with emerging flaky tests;
- how to implement the solution in CI and build a reporting system that everyone will understand.
All solutions will be shown on the example of a specific demo application. This application you can see on GitHub. People can use ready-made solutions in their work.
The purpose of the talk: to show people how certain problems in UI testing automation of Android application are solved (case by case). These solutions don’t require reworking the application architecture or any significant revision for autotests.
About Aleksei Tiurin
Engaged in testing automation for over 7 years. Started from automation of banking platform on a C-like language. Developed web application autotests on Selenium and Java. Has been engaged in testing automation of Android application for 5 years. During that time he tried various automation tools from Robotium and Appium to Espresso. Tries to promote automation in all areas of testing. Initiate of Kotlin and Espresso in Android development.
Interesting and quite obvious fact: Alexey doesn’t use Facebook.
VK, Lead Android Automation Engineer