Test Automation Beyond Java 8

Abstract
While most people are still using Java 8 from six years ago, new versions of the language are being released every six months! The latest versions provide an abundance of new features such as functional programming capabilities, switch expressions, local variable type inference, additions to the Stream API, new factory methods for Collections, text blocks and much more.

With so much content, your Java upgrade should be more than simply the update of a jar file. Your test code no longer has to be as verbose as it once was, meaning less code to write and maintain!

This talk will introduce the new features of Java 9 – 14 and provide examples of how these features can be used for test automation.

Key Takeaways

• Introduction of new features in the latest 6 releases of Java (9 – 14)
• Examples of how the features can be used for test automation projects
• Greater command of the programming language

Bio
Angie Jones is a Senior Developer Advocate who specializes in test automation strategies and techniques. She shares her wealth of knowledge by speaking at software conferences all over the world, teaching courses, and writing tutorials on angiejones.tech. 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.

The Truth About Oracles

Abstract
There’s a tranquil air through the office, but it’s about to be disrupted by the all too common, but often encouraged, flash of red. POP! The red flies through the office catching everyone’s attention. It’s mostly greeted by curiosity, but several people are well on their way to seeing red themselves! “Is there a problem here?”, no, just the power of oracles.

There are numerous reasons a build can fail, but the one I’m going to be focusing on for this talk is failing automated checks. I absolutely love automated checks, they are a powerful force when it comes to delivering valuable software at pace. The speed at which they can provide actionable feedback is invaluable, but that actionable feedback is based on a well-designed oracle. If the term oracle is new to you, think about your assertions, but it’s important to note that oracles and assertions are not the same.

I’m going to share my journey of studying oracles with you, exploring how the identification of your oracle is crucial in the design of your automated checks. How tools should follow your oracle, and how dangerous it can be to design oracles based on your tools. Exploring the different types of oracles, and how understanding them impacts the feedback you gather, and your automation decisions. How costly the time spent understanding the reason your checks failed can be, and how this can be significantly reduced when a clear oracle is identified and the check built around it.

Every single one of you has oracles, utilises them, talks about them and creates them. Being aware of how that happens, what they are, and codifying them into your automated checks, will elevate your checks to new heights.

Key Takeaways

• Describe what oracles are
• Compare and contrast different types of oracles
• Identify the right tooling to codify your oracles
• Communicate the importance of oracles
• Understand where oracles come from
• Understand the importance of naming your checks to identify the oracle

Bio
Richard Bradshaw is an experienced tester, consultant, trainer and generally a friendly guy. He shares his passion for testing through consulting, training and giving presentations on a variety of topics relating to testing. With over 12 years of testing experience, he has a lot of insights in the world of testing and software development.

Richard is currently the BossBoss at the Ministry of Testing, co-creator of the Automation in Testing (AiT) namespace and blogs at https://automationintesting.com.

Setting Up Your Tests To Fail

Abstract
We often have automated UI tests for features that we know aren’t working right. Defects, API issues, and more…but when the team has decided that the behavior isn’t going to be fixed, what’s an automation engineer to do? Jenny Bramble suggests writing your tests to pass.

By creating tests that pass on the current expected behavior (even if it is objectively incorrect!), we can create tests that are meaningful and actionable because they return information on the current state of the application—without creating more failure fatigue in our team.

Key Takeaways

• Automated tests are information, not bug detection systems
• Automated tests should pass on EXPECTED behavior even if that behavior is objectively a defect (AKA designing to fail)
• TODOs, documentation, and other methods to keep your team informed of the expected behavior of your automation suite

Bio
Jenny came up through support and DevOps, before diving headlong into her career as a tester. Her love of support and the human side of problems lets her find a sweet spot between empathy for the user and empathy for her team. She’s done testing, support, or human interfacing for most of her career. She finds herself happiest when she’s making an impact on other people—whether it’s helping find issues in applications, speaking at events, or just grabbing coffee and chatting.

Automating Tactically and Strategically

Abstract
One of the biggest concepts that has made a difference to my programming and automating in recent years is the concept of “Tactical vs. Strategic.” Automating tactically might be for a specific purpose, possibly small, possibly a bit rough around the edges, not necessarily completely robust for everyone, etc. And Strategic automation is more critical to long-term aims, maintained and maintainable, etc. In this talk, Alan Richardson will provide examples of automating both Strategically and Tactically for activities as diverse as supporting testing, marketing and general life. We will also consider how and when to move from automating tactically to strategically, and how the concept has helped me change my programming style and how to write better code.

Bio
Alan Richardson has more than twenty years of professional IT experience, working as a programmer and at every level of the testing hierarchy from tester through head of testing. Author of the books “Selenium Simplified” and “Java For Testers”. Alan also has created online training courses to help people learn Technical Web Testing and Selenium WebDriver with Java. He works as an independent consultant, helping companies improve their use of automation, agile, and exploratory technical testing. Alan posts his writing and training videos on SeleniumSimplified.com, EvilTester.com, JavaForTesters.com, and CompendiumDev.co.uk.

TITLE COMING SOON

Abstract
COMING SOON

Bio
COMING SOON

Testing the Mesh – In a Culture of On-Prem

Abstract
Modern cloud-native business apps are inherently distributed, introducing immense challenges across the complete development lifecycle. They require new ways of developing, deploying, and delivering apps, resulting in a total overhaul of the production process. Breaking down historically-grown monoliths and forming smaller building blocks is critical to reduce per-tenant cost, promote agility, and facilitate seamless integration.

SAP piloted the approach with some of its products – facilitating change – both in technology and in cultural aspects. With modern tools, complex microservice applications are delivered daily, implicitly ensuring high-quality standards by using innovative automation and testing techniques. To ensure business continuity and keep customers’ mission-critical processes running, we’re using feature toggle configurations, A/B activation strategies, and strong resilience.

Key Takeaways

• Cultural change and flexible tools are equally critical for overall success
• Get the teams engaged – everybody’s responsible for product quality
• Speed matters – aim for the lowest possible meantime from commit to testing results
• Integrate early – to avoid late surprises and frustration
• Importance of unit vs solution-level testing

Bio
COMING SOON

Not Your Parents’ Automation – Practical Application of Non-Traditional Automation

Abstract
Most software companies have an automation initiative. Typically, these initiatives focus on “traditional automation,” using a software package to automate existing test cases or user stories. Not that there’s anything wrong with that; often, there is value in that method. However, if we use only this traditional approach, we miss opportunities to exploit the power of automation. Instead of focusing on test cases, what if we consider this: how can automation help me best do my job?

During this session, Paul Grizzaffi will share real-world examples where non-traditional automation (or “automation assist”) provided business value, highlighting cases where the traditional method could not have provided the same level of testing; you will hear High Volume Automated Testing (HiVAT) highlighted as one of these approaches. You will also hear thoughts to keep in mind when implementing automation assist and see examples of creating helpers from tools not traditionally used for automation.

Key Takeaways

• Traditional automation can be valuable, but do not be blinded by the typical approach
• Ways to utilize automation to help you do your job efficiently
• There is more than one way to use your tools

Bio
As a Principal Automation Architect at Magenic, Paul Grizzaffi creates technology solutions for testing, QE, and QA organizations, including automation assessments, implementations, and through activities benefiting the broader testing community. An accomplished keynote speaker and writer, Paul has spoken at national conferences and meetings; he’s a guest lecturer at UT Dallas. When not spending time with his twins, Paul enjoys sharing with and learning from other testing professional.

Testing the Mesh – In a Culture of On-Prem

Abstract
Modern cloud-native business apps are inherently distributed, introducing immense challenges across the complete development lifecycle. They require new ways of developing, deploying, and delivering apps, resulting in a total overhaul of the production process. Breaking down historically-grown monoliths and forming smaller building blocks is critical to reduce per-tenant cost, promote agility, and facilitate seamless integration.

SAP piloted the approach with some of its products – facilitating change – both in technology and in cultural aspects. With modern tools, complex microservice applications are delivered daily, implicitly ensuring high-quality standards by using innovative automation and testing techniques. To ensure business continuity and keep customers’ mission-critical processes running, we’re using feature toggle configurations, A/B activation strategies, and strong resilience.

Key Takeaways

• Cultural change and flexible tools are equally critical for overall success
• Get the teams engaged – everybody’s responsible for product quality
• Speed matters – aim for the lowest possible meantime from commit to testing results
• Integrate early – to avoid late surprises and frustration
• Importance of unit vs solution-level testing

Bio
COMING SOON

Accessibility Testing for Mobile Applications

Abstract
Imagine for a moment that all our mobile applications are inclusive for most of the disability profiles. Imagine that it is easy to redact acceptance criteria for accessibility, and that all QA team players are trained to test the E2E flow through immersive techniques. And if you really are a dreamer, imagine that the automation framework and emulator allow us to automatize easily all the accessibility acceptance criteria.

It might seem to be a utopic ideal that’s far from reality, but this talk will show you how to work towards this vision. The first step is to define, in collaboration with User Research and UX teams, the different user profiles to target. Designing and developing accessible screens for mobile applications is only the first step to reach the accessibility goal. But testing the accessibility of the application is challenging to say the least. You’ll learn what can be done now, and what we can hope for in the future.

Key Takeaways

• The different disability profiles that we should take into account when developing an application
• Accessibility rules for developers
• How to choose a testing tool for accessibility
• A discussion of what we can expect from the future

Bio
With more than 10 years of experience in QA and IT in general, Hélène is now Engineering Manager for a team of 10 QAs, in Cabify, a Spanish unicorn start up company. She participated in international projects in several industries: travel, ecommerce, mobility, etc. Hélène is a fervent advocate for diversity in tech, she has collaborated with a lot of initiatives to give more visibility to technical women.

What’s in a Name? Metadata for Fun and Profit.

Abstract
We’ll start with a rundown of what makes useful Metadata, and what Metadata is, exactly. We’ll move on to looking at why test names should be Fables, not Filing Cabinets, learning what makes test names good, and what makes them bad.

We’ll talk briefly about test Status and how Exceptions aren’t Exactly Errors, before covering how and why to use Build IDs, Tags, and Custom Data.

This talk is for everyone in QE; we’ll have minimal code examples, no assumption of prior knowledge and most of what we’ll cover applies to non-Sauce Labs customers.

Key Takeaways

• Practical information about how to best name tests
• The ability to think more critically about test failures
• Suggestions on how to use tags, build IDs and custom data to organize and share tests better

Bio
Dylan has worked for Sauce Labs for seven years, helping customers learn & solving problems. His passion is sharing knowledge and making people’s lives easier through technology, which he’s been doing for 14 years. He’s been involved in Evangelism, QE & Development, as well as Product Design and Marketing across Fintech, Transportation, Data Warehousing and Health. He promises he’s not as boring as he sounds; Follow him on Twitter, @dylanlacey, and he’ll prove it!

Breaking Boundaries Using Charles

Abstract
Quite often we struggle to test all scenarios due to the limitation of test data. This applies especially when apps rely on third-party services and testing at different territories is required. Depending on the testability of your product, it can be hard to check all corner cases if the production back-end must be used and cannot be tricked. With a proxy, you can change what will be displayed.

Charles Proxy is known as Man-In-The-Middle and is loaded with features. Charles not only allows us to learn more about how our app functions the way it does, but it also opens our eyes to an entirely new array of testing possibilities to explore, from visualizing a simple request to mocking data from an existing or non-existing endpoint. During this session, Suman will show you how Charles Proxy can help to identify the cause of the bug that relates to your app making/receiving network calls/responses.

Key Takeaways

• How to use Charles on iOS and Android devices
• Observing and modifying HTTP requests and responses
• Rewriting using map local and remote
• Network throttling
• Whitelist and blacklist URLs

Bio
Suman Bala is Quality Lead at Sky. She strives to mature testing practice as a key enabler to drive business change benefits and is a strong believer in test automation. She is a quality evangelist who is passionate about providing continuous value adds through leadership, problem solving and encouraging efficiency. Sumanhe is co-organizer for the Ministry of Testing Leeds meet-up and actively involved in Women In Tech, Better Allies, and Grassroots Leader initiative groups.

Building Trust In Your Automation Using Virtual Services

Abstract
For as long as automation teams have been using Selenium, they have struggled with the challenge of managing test data. How do we manage the state our tests require? Even more important, how do we manage the state in between test runs?

Many times, we resort to creating test accounts in specific states or initializing the state via UI during setup. We then revert the state after test run in a teardown or via a post test script. But this adds another cause for failure and, at times, requires manual intervention.

With virtualized services, tests can manage the data they require. Additionally, the test environment no longer needs to rely on unreliable development web services. The result is a less flaky test suite and a purely isolated front-end integration test run.

Mathew will share some of the challenges he’s faced and how he achieved a stable continuous testing pipeline utilizing virtual services.

Key Takeaways

• Learn how to leverage service virtualization to overcome their test data challenges
• Be introduced to virtual service tools, like Wiremock, and service interceptors, like angular in-memory web api.
• Understand how using virtual services provides faster and more consistent test runs.

Bio
Mathew Cano has 15 years of experience in test engineering with over 10 years in building test frameworks and CI/CD pipelines. Over the years, his role has ranged from manual testing, to writing automated tests to mentoring and pairing with developers on writing maintainable and reliable tests, whether unit, functional or integration. Mathew has embraced the continuous testing mindset and is passionate about improving developer efficiency through tooling and automation. He currently works as a Sr. Software Development Engineer in Test at Charles Schwab.

A Beginner’s Guide to Test Automation

Abstract
The options for automation are wide open, and you may feel overwhelmed with questions when you’re getting started: “What tool should I use? Which tests should I automate? Why is automation useful for us?”

The goal of automation is to create anti-fragile tests that are easy to understand and maintain. I’ll help you achieve that goal by answering questions that I ran into when I first started.

Key Takeaways

• What to consider when you’re choosing a tool or framework
• How to decide which tests to automate
• Best practices for writing the tests, like granularity and failure messages
• A feeling of confidence that you know how to get started

Bio
Angela Riggs believes that empathy and curiosity are driving forces of quality. She appreciates the hikers’ approach of “leave it better than you found it” and strives to do the same, whether it’s people, processes, or the organization as a whole. Her experience ranges from feature testing to leading company-wide process changes, and she enjoys her work most when she is supporting people to do their best work. Angela is also a strong advocate for a safe and inclusive environment.

Not Just Accessibility IDs: Speed Up Your Appium Tests for Faster Feedback

Abstract
You want to be able to deliver at speed, so you want test automation for your mobile apps. But your suite is large. The tests are slow. You run them overnight. You split the tests over nodes. But it still takes hours to run. In this session, Hugh McCamphill will discuss a number of ways his team was able to speed up Appium tests to run 20-40% faster, beyond the use of accessibility IDs; for example:

• Which Appium capabilities sped up our tests
• Which Appium abstractions slowed us down
• The value of reusing discovered elements

Key Takeaways

• How to better understand what is time-consuming in a test
• The value of and how to rethink assertions to reduce test execution time
• Multiple strategies are required to speed up tests

Bio
Hugh McCamphill has been involved in testing for more than 15 years. While interested in all areas of testing, he specializes in test automation. He is currently a Test Engineering Manager with ShopKeep in Belfast. Hugh is also keenly involved in the testing community and organizes the Belfast Selenium Meetup since 2013. He also helps organize the Software Testing Clinic in Belfast.

Pinterest’s Philosophy of UI Testing

Abstract
At Pinterest we use UI testing as a tool to ensure quality and improve the quality of life for hundreds of developers. In scaling our UI testing, we’ve learned first hand what works and what doesn’t work. Eventually we cemented it into an internal guide for thinking about UI testing. This presentation will share how we think UI tests should be written and when they should not be written.

Key Takeaways

• An understanding of how UI test strategy fragmentation is an inevitable problem if not actively addressed
• How to align testing strategies between platforms (iOS, web, android)
• How to align testing strategies between teams
• How Pinterest scales UI testing

Bio
Ryan Cooke has worked at a series of small startups. At Pinterest, he found a lot of success in helping the Android team scale through a variety of regression testing. He also has taken over the company’s testing strategy. In his spare time, Ryan is also the reigning champion of Super Smash Bros tournaments featuring over 60 employees from a handful of San Francisco Tech Companies.

How To Lie With Test Automation Metrics

Abstract
Phil Wells is a senior software engineer for the New York Times crosswords and games group. In this diabolical anti-talk, he will reveal the time-worn nasty secrets handed down through generations of test and QA professionals. Automation engineers love measuring things like code coverage, browser coverage, build time, and pass/fail rates for one very simple reason.

These stats can be cheated.

Ever the bad influence, Phil will lead a seminar in how to use these metrics to drive a practice that is solely for the purpose of beefing up those metrics. Real software testing, he will reason, is not about limiting rework or ensuring confidence in a team’s software delivery process. It’s about those numbers. It’s about validating the existence of the practice itself. More than anything else, it’s about looking out for number one.

Then, at the end, Phil will drop the pretense and talk about a couple of metrics that are actually fine and how we can measure those.

Key Takeaways

• Anti-patterns in designing and managing test automation projects, and better alternatives
• Effective (and ineffective) indicators that automation efforts are yielding positive results for your team
• How to trick your manager into thinking you’re doing a ton of work with the magic of statistics 😉

Bio
Phil Wells has been a software quality practitioner for over a decade. Now, Phil is a senior software engineer with the New York Times crosswords and games team. This team maintains the most popular crossword product in the world. Phil works to ensure that this team builds quality into every new feature and game they deliver.

Building Better Relationships with Your Dev Team

Abstract
Much like devops used to be seen as two different departments with competing goals, QA and Dev can be treated as incompatibly different. Many companies will say they buy into the idea of quality being everyone’s responsibility, but when a major bug gets to prod, the response doesn’t always match.

Using a variety of examples from real experience, Julie Laursen will talk about how you can build credibility, trust, and respect by being a steward and advocate of best practices. She’ll talk about submitting good bug reports, contributing thoughtfully to reviews, and how your manual testing experience is still valuable. I’ll also review how I personally leveled myself up technically as an automation engineer.

Julie will illustrate how you can be seen as a peer with complementary skills if you manage the relationship right, and how that relationship can go off track with stories of my own missteps. If your current situation is one with existing tension, I’ll talk about when and how to improve those situations or when to jump ship.

Bio
Julie is one of the co-organizers of Austin Automation Professionals. She has approximately six years QA experience and is currently at Keller Williams. She was previously at AT&T for eight years in various roles such as QA, NOC and management. Julie holds a Masters in Business Administration, Bachelors in Information Systems Technologies, and an Associates in Computer Programming.

NativeScript’s Journey to Mobile CI in the Cloud with Appium, Travis and Sauce Labs

Abstract
When it comes to testing open source software, you should have a primer showing the community how to use best practices to achieve a stable CI process, visible to all. And if something must be accessible from everywhere and from everyone, there is one place to do that—the cloud.

In this session, Dimitar Todorov will show one of their approaches to transparent CI process in the cloud with zero local infrastructure, using popular services like Travis-CI, Sauce Labs and GitHub. The session will also provide visibility for contributors and product owners on how it works and how quality of the software is achieved.

Bio
Dimitar Todorov has been testing software for more than 7 years now and has worked on different projects and cloud platforms for mobile application development. He is currently working on the NativeScript team as a Senior Automation QA engineer. His passions include continuous Integration, performance testing, and automation, and he has experience in almost every aspect of software testing. Dimitar is certified with all advanced ISTQB certificates and is especially interested in mobile application testing.

Orchestrate Your Parallel Testing to Be a Symphony with TestNG

Abstract
When it comes to running parallel tests against the Selenium grid or Sauce Labs VMs, you don’t have to think about coordinating your resources (as much). But what if your resources are limited and you’re constrained by the number of devices of a specific OS/Browser version and you still want to run your tests in parallel? Is it still possible? This presentation will go into the depths of parallel testing with TestNG and provide you with tips and tricks on how to manage/coordinate your parallel executions.

Key Takeaways

• The do’s and don’ts of parallel testing
• An understanding of the strengths of TestNG (e.g. Listeners/Interceptors/Custom Annotations)
• Helpful tips for debugging

Bio
As QA Technical Architect with over 10 years of experience in the field of automated testing, Sergio Neves Barros has worked on automating technologies such as HTML 5, Canvas, Flash, native apps and REST APIs. He has contributed to the Appium project to expand its capabilities of testing with Safari on physical iOS devices. Throughout his career, he custom built many frameworks based on business needs and mentored others on the best practices of building/maintaining their own framework.

Designing a Unified Developer Framework for Functional and Performance Testing

Abstract
Is the high cost of maintaining separate automated functional and performance tests from a select pool of experts versus from any developer within your organization hurting your bottom line to quality, productivity, and speed? Would you like the opportunity to decrease the overlap of creating and maintaining these scripts along with its associated infrastructure? Paychex is extending its TAF (Tool Agnostic Framework) from a DSL (Domain Specific Language) script creation approach to a Python coding script creation; this will be done by providing TAF libraries to developers. Paychex will also continue to co-design its new Test Services framework that will provide both functional and performance testing within one solidified platform. This initially provides better Single User Performance (SUP) testing which sets the stage for ideal load creation. This session will share TAF’s current framework that supports over 70K executions per day as well as the early design challenges of creating the new Test Services framework. All of this is designed to directly feed our CD (Continuous Delivering) initiatives.

Key Takeaways

• Business drivers for having both Keyword Driven and Python automated test scripts
• Design decisions to integrate Keyword and Python architectures
• Functional tests to gain early insight into application performance
• Early design decisions to synthesize non-ui and ui performance data

Bio
Danny McKeown has both senior technical and management experience in information technology. As the Senior IT Automation Architect at Paychex, he is instrumental in implementing a secure integration of test automation technologies as part of their continuous delivery solution. Danny is an adjunct lecturer at RIT , sits on the advisory board for IIST, and is a frequent speaker at numerous technology forums.

The Perfect Score: How Quick Base Aced the Continuous Testing Benchmark

Abstract
Continuous Testing is a proven method to help engineering organizations deliver better quality software faster. However, for many teams it can seem like an insurmountable effort. With cultural hurdles, technical challenges, and a variety of stakeholders involved, it is often a long and arduous journey to the Continuous Testing “promised land.” However, when equipped with a plan for success, measurable goals, and a unified team working together, results are achievable.

This session will focus on:

• How to ensure that quality has a seat at the executive table, creating alignment on testing strategy from the beginning.
• Implementing “drama-free” technologies and consistent practices that are optimized for broad adoption across multiple development teams.
• The ongoing partnership between QA and Development teams, and how to provide continued engagement, support and education.

Using this foundation, Karen will show how Quick Base drastically improved its quality outcomes, increased efficiency by breaking down collaboration barriers with development teams, and created a true culture of quality in her organization.

Bio
Karen Motyka has been in the quality industry for a number of years and in a management role for the past 12 years. She established and manages both a System Quality Team and a Quality Community of Practice at Quick Base. Focus within these groups has been on supporting framework, infrastructure, and tools needs, enabling teams to move more quickly through process and best practice advancement, and up-leveling quality expertise across the organization. She’s passionate about quality (of course), leadership, and team management. She’s received leadership awards from several programs including the Women Unlimited LEAD Program and Dale Carnegie.

Sauce Connect On Demand – A Flexible Tunnel Strategy

Abstract
The test automation team at Dell has expanded their offering for their development teams since they started running SauceConnect on Kubernetes. Morgan Vergara noticed that since they can quickly and easily create tunnels using Kubernetes, they began receiving a lot of ad-hoc tunnel requests. Rather than continuing to respond to these requests manually, they did what any developer would do: they automated it.

In this session, Morgan will describe the current Dell environment as well as their on-demand architecture.

Key Takeaways

• A more thorough understanding of SauceConnect
• An understanding of Dell’s complex development environment
• A new way to use SauceConnect tunnels in a more complex environment
• The pitfalls we’ve encountered with our tunnel strategy

Bio
Morgan Vergara has been doing software development for 30+ years, most of it at Dell since 1992. They wrote their first line of code (FORTRAN, for the curious), in 1978 and never looked back.

Using ML to find value in your automated tests executed in Sauce Labs

Abstract
Today’s modern development disciplines—whether Agile, Continuous Integration (CI) or Continuous Delivery (CD)—have completely transformed how teams develop and deliver applications faster. But in order to compete in today’s fast-paced digital economy, companies must also test faster and test continuously. To do this, you can use remote and scalable infrastructures like Sauce Labs to track test results of thousands of tests for hundreds of runs, triggered by code changes.

What if we could use Machine Learning to find value in automated tests and reduced time of result analysis, executed in Sauce Labs? In this presentation, Dmitriy Gumeniuk will share details about an open source AI-powered test automation dashboard— ReportPortal.io, which integrates with Sauce Labs for real-time reporting.

Key Takeaways

• Learn how to start ReportPortal.io on your project to organize dashboards and metrics tracking.
• Leverage API of the tool for integration with CI tools like Jenkins.
• Make strides toward continuous testing by bringing in security and performance testing results in one single entry point of testing results for your team.

Bio
Dmitriy Gumeniuk is the Delivery Manager, Product Manager at Epam Systems, a leading global provider of digital platform engineering and software development services. Dmitriy leads development of solution accelerators at the Test Competency Center, focusing on the usage of Machine Learning and Neural Networks in test automation. While 13 years in software development, he provides technical leadership for Java development teams to advance test automation at any scale. Dmitriy also contributes to the local DevTestOps community by leading local meetups, actively speaking at events in CIS and eastern Europe, and organizing the DelEx Conference.
Product Owner of ReportPortal.io

Mobile Security Testing With Fuzzing – From Google Project Zero to ABN AMRO

Abstract
From Google Project Zero to dangerous state sponsored hackers, almost every recent mobile security vulnerability has been identified with Fuzzing.

At ABN AMRO we are introducing this methodology in our QA process as an effective, cost-efficient way to identify and later on fix security issues in our mobile applications.

Key Takeaways

• Zero days vulnerabilities in mobile apps
• Looking for bugs and vulnerabilities with Fuzzing
• Examples of Fuzzing
• Innovative ways of doing fuzzing: Neural Fuzzing
• Fuzzing mobile apps using Saucelabs

Bio
Sergio Giucastro is a software engineer with a strong background in reverse engineering, hacking and IT security. In the last 10 years has been working on many commercial Android apps. He is currently working in ABN AMRO contributing to make the mobile applications (iOS and Android) safer.