Reduce test scripts execution time by Deeplinks
This Talk will be having :
What Deep link is & How we can make effective use of these links to reduce the overall execution time of our scripts.
Why we should use deep link ??
There are some scenarios where we have to follow some navigation steps to reach the actual page for validation. Deeplinks helps us to skip this unnecessary navigation and lends directly to required page and hence reduce execution time of our Test case script. We use Mainly for:
- Reduce execution time
- Reduce the amount of failures that are caused due to navigation through the app
Deeplink helps us to directly lend on required page.Deep linking is a fancy way to refer to a URL that points to a specific part of an app. It’s analogous to a URL that points to a subfolder of a website. For example if I wanted to send you a message page of linkedin, I would send you a URL that immediately brought you to the message page, not send you to the home page to navigate to it yourself from there.
Eg: We have following flow of our app:
Page A > . Page B > Page C > Page D and we have validation test on Page C only.
So rather than going through Page A to Page B to page C, We can directly lend to Page C using Deeplinks & hence reduce the time efforts.
Where can we use deeplinks?
These links are most suitable for mobile app Testing (iOS and Android)
I tried this strategy in one e commerce website Test case steps:
Scenario Used –
- Create user via api with saved CC, saved shipping address and added products in basket
- Navigate to home page and sign in (Deeplink used)
- Navigate to basket (Deeplink used)
- Navigate to checkout and place order (using UI )
- Navigate back home page from order confirmation page (Deeplink Used)
We came up with following time difference:
- Execution time without deeplink – 5 min 01 sec
- Execution time with deeplink – 3 min 46 sec
For this sample script which will be mentioned above, difference in the execution time(1 min 15 sec) is significant.
We'll also showcase the code snippet for this.
Outline/Structure of the Tutorial
Its a discussion on using Deeplinks in test automation scripts
- Understanding of deeplinks
- How to use deeplinks in required areas
- Better outcome in terms of Execution time.
Prerequisites for Attendees
A small understanding of deeplinks
schedule Submitted 10 months ago
People who liked this proposal, also liked:
Khyati Sehgal / Shubhechchha Rai - Applying software craftsmanship to the evolving world of automation.Khyati SehgalQuality Lead3 Pillar GlobalShubhechchha RaiAutomation Quality Analyst3 pillar global
schedule 10 months agoSold Out!
Software Craftsmanship is a practice of continuous development and helping others learn the craft. As the world is evolving towards the era of scripting language, we will be sharing our experience of how we have grown as a team of all QA with programming language background to the niche typescript world contributor.
During this talk, we will be focussing on the shift of existing selenium to the actual implementation of Protractor test API. How and when to use a protractor? When to pick protractor as an automation tool for building a framework.
We will also talk about configuration files, cucumber, typescript, promise handling in protractor.
Khyati Sehgal / Shubhechchha Rai - Expanding the aura of automation, when it comes to mobile.Khyati SehgalQuality Lead3 Pillar GlobalShubhechchha RaiAutomation Quality Analyst3 pillar global
schedule 10 months agoSold Out!
This talk will answer the questions "Will you be able to run your automation scripts without connecting the USB cable to your device in a limited range?"
If we have to ask ourselves where is the mobile and when is it required? So the answer would be its 'Everywhere'!!
It's next to possible to imagine a day without looking at mobile or using apps for that matter- Google, Facebook, Whatsapp, etc.
When it comes to using it so testing comes hand-in-hand with it. As we develop applications over a mobile device, be it any platform ios, Andriod and windows we shall also think about usability and end-to-end testing.
In this talk, we will discuss how Appium worked as a bridge between devices and controllers.