Varuna is a technical tester who's worked on award-winning projects across a wide variety of technology sectors ranging from retail, travel, financial and the public sector; working with various web, mobile, and IoT technologies. Varuna is a passionate advocate of shipping quality code to production using Agile practices. When not working, Varuna likes to get her hands dirty on experimenting on her culinary skills. Most of her weekends are spent in C()()kgraphy i.e. Cooking +Photography!
In this session, Varuna will share a specific case study of how an effective test strategy can get away from Push and Pray deployment to Continuous and Confident deployment to production.
This is a case study of the product, where the very first thing I observed was unclear roles and responsibilities within the QA of an organization. There was a low test coverage as there was no clear testing strategy to follow. Getting deployed to production was Push and Pray method which led to high risk for production. It was also causing inefficient use of QA timing. There was the pain felt throughout the organization in a smaller group and folks kind of accepted this pain. We started with noting down the pain points of producer and consumer teams within organizations and even a third-party team to come up with an effective test strategy of the product.
Participate in this talk to learn:
1. How we formed a core team to define the external and internal strategy?
2. How did we apply recursive feedback and updated the strategy when and required after a production release?
3. Internal Test Strategy: A strategy within a Team of the same vertical as checkout API and UI
4. External Test Strategy: An end-to-end test strategy of a product
5. How did it help in getting away from Push and Pray deployment to Continuous and Confident deployment to production?
We got the motivated QAs across the organizations and better quality products with a Test Strategy across organizations. It had also helped in mapping a QA learning curve with a test strategy within an organization
Participate in this workshop to learn how to put together the advanced concepts of a wdio and typescript in a mocha framework that is scalable, robust, easy to read, and eliminates the brittleness in your checks. We will be sharing our real-time experience of how we migrated our testing approach, design and framework when our enterprise application was migrating from monolithic to a microservices architecture.
This workshop will introduce you to new advanced techniques design patterns and teach you how to break down large, flaky UI tests into quick and simple ui tests. You will be given practical hands-on experience on preferred design patterns while designing a framework and on completion of this interactive workshop you will leave with your very own example automation framework that demonstrates advanced principles of wdio using typescript automation design. We will integrate with allure reporting.
In this session, Varuna will share a specific case study of how e2e automated tests for flutter mobile apps can get away from capturing manual screenshots to automated screenshots for auditor approvals
A mobile app has immensely become a part of everyone’s life these days. People are moving from desktop to mobile apps to get their daily need been served. It becomes very important how fast your mobile app works, what glitches you face on poor/no network connection.
So, testing these apps becomes very important from Go to market perspective and how would you invest automating those user journeys and personas
A new baby named “Flutter” by google came into the market for building mobile apps.
We are building a mobile platform using Flutter, which provides a flutter driver package to write your automated e2e integration tests.
In this talk I will share how we started using flutter driver for our e2e automated tests, You will get to know how you can get started from beginning and building flutter driver tests for your mobile apps. A talk will cover initial setup and demo with running e2e automated tests using flutter driver.
Participate in this talk to learn:
1. What were our initial challenges in less community support and what were workarounds?
2. How we incorporated third-party plugins to run the tests?
3. How it helped in our mock trading days when you have to provide evidence to auditors for approvals?
4. How we integrated with the cloud service provider to run these tests?
5. What are the current limitations in flutter driver?
At the end of the session, you would have the understanding to start automating flutter mobile apps
Over time, we had created a significant set of Selenium tests which we were running over a Selenium Grid. The runtime had reached five hours, and we were feeling the pain in the feedback delays which revealed the need for parallel execution. Previously, we used the Selenium Grid Docker container for each test run. This way, we were able to run 5 concurrent threads for test execution, which took an average of 45 minutes.
We had to scale test but we couldn’t run more than 5 concurrent tests as the containers hit performance issues and we had a hard time getting reliable tests outcome. This led us to move to AWS Lambda.
In this talk, I will explain how we started with a very small suite of five tests to first build the AWS Lambda infrastructure, learn to use the tools of working in the new environment and achieve reliability of the test runs over a timeframe of 45 days. I will walk you through how we selected to move all tests in feature-based batches, with a continuous focus on the reliability of the tests. I will explain from our challenges on the way to now run all our tests within the timeframe of the longest test, improving our feedback time significantly.
As part of Demo, I will walk through a sample project in Github where I will explain how we can scale our UI tests using AWS lambda.
Outline/structure of the Session
1. Challenges faced in the project and why we moved away from selenium grid to Lambda.
2. What is AWS Lambda and How does it work?
3. How does AWS Lambda help in scaling tests?
4. Recorded Demonstration:
How to write a first lambda function.
How to run and scale the tests.
How to view results in aws console.
How to get started with writing the first lambda function
How to make your existing test run as part of Lambda.
How to set up infrastructure in AWS to run tests there
How to focus on reliability in small batches
What are the differences in running tests on AWS Lambda vs Selenium Grid
Participate in this workshop to learn how to put together the advanced concepts of an API test in a
a framework that is scalable, robust, easy to read, and eliminates the brittleness in your checks.
We will be sharing our real-time experience of how we migrated our testing approach, design and framework when our enterprise application was migrating from monolithic to a microservices architecture.
This workshop will introduce you to new advanced techniques design patterns and teach you how to break down large, flaky UI tests into quick and simple API tests.
You will be given practical hands-on experience on preferred design patterns while designing a framework and on completion of this interactive workshop you will leave with your very own example automation framework that demonstrates advanced principles of api test automation design. We will create a poll to select a language(Java, C#, typescript) in which you preferred to
design and use that framework.
Outline/structure of the Session:
Basics of rest principle.
Api architecture and types of api testing.
Do’s and Don’t’s of api testing.
Create a framework
a. Add e2e functional tests using API’s.
b. Introduction to design patterns and error handling.
c. Handle the performance testing of API's.
d. Add checks for security threats.
5. Brief on how can a framework be enhanced?