RPA using Power Automate Desktop Tool >> Changed our Automation Perspective from Complex code to Simple flows

Spreadsheets have a dominant way of managing multiple business processes.

Validating these spreadsheets data points manually is very hectic and automating them needs knowledge on scripting. Also automating spread sheet actions like handling excel popups ,clicking macro buttons etc., will require more efforts.

RPA Power Automate for desktop provides an extensive variety of Microsoft Excel Spreadsheet actions to help you read and manipulate Excel files. With this RPA ,we handled spreadsheet actions using simple flows with out complex scripts. Simple drag and drop flows changed our view from the usual mind juggling of code/scripting concepts to simple business actions. This indeed saved lot of time and efforts.


Outline/Structure of the Case Study

> Introduction and Problem Statement - 5 min

> Solution with RPA Power Automate Desktop - 10 min

> Benefits - 3 min

> Q&A - 2 min



Learning Outcome

Automate complex excel spread sheet activities in less time with no code concept.

Target Audience

Software Testing Professionals

Prerequisites for Attendees

No Pre-requisites required


schedule Submitted 9 months ago

  • Robin Gupta

    Robin Gupta - TestZeus: Open source UI automation framework built specifically for Salesforce with Auto-locators

    Robin Gupta
    Robin Gupta
    Associate Vice President
    schedule 11 months ago
    Sold Out!
    45 Mins

    Automation for Salesforce is tough (no , seriously). And every platform release brings the lightning and thunder for UI Automation tests (Winter21 caused even our tests to shiver). So we present TestZeus to end this madness and create a simple (and robust) Open source framework for Salesforce Test Automation. And solve the problem of flaky tests, while accelerating the development of automation .

  • Eran Kinsbruner

    Eran Kinsbruner - Comparing Selenium 4, Cypress and Playwright Frameworks

    Eran Kinsbruner
    Eran Kinsbruner
    Global Evangelist
    schedule 11 months ago
    Sold Out!
    45 Mins

    As the cross-browser testing landscape evolves, there is a stabilization around 3 main leading frameworks that are used the most. Some are more adopted by frontend developers, while some are adopted by SDETs. To better make a selection or even choose more than a single framework you need to realize the core differences and use cases as well as benefits each framework provides to the practitioner.

    In this session, Eran Kinsbruner, Chief DevOps evangelist, best-selling author from Perforce (Perfecto and Blazemeter specifically) will go through the core differences and advantages of all 3 frameworks with focus on Selenium 4 vs. the latest versions of Cypress and Playwright and provide a nice outline to better guide test automation engineers as they look for their next test framework.

  • Ragavan Ambighananthan

    Ragavan Ambighananthan / Dan Adajian - A story of real implementation of Shift Left

    45 Mins
    Case Study

    This is a real story of how we implemented Shift Left by influencing, mindset change, creating champions and with the help of technology at Expedia Group.

    In every software company in the world, at the nucleus of it, all we are trying to do is, take a code change and move it to production, faster with quality. There couldn't be any disagreement over this!

    Sometimes when we repeatedly follow a practice, even when there are new better alternatives, it is difficult to change our mindset because we think "Why change? it is working".  Moving your pipelines to follow Shift Left is one of them.

    In US alone, $113B is spent annually on identifying and fixing production defects!

    Shift Left not only increases developer productivity, but allows you to go to production faster, more frequently and reduce production incidents. End of the day, it makes both developers and customers happy!

    The biggest frustrations for developers in a team is, CI/CD pipeline being blocked and no one can merge their PR, everyone has to wait for it to be fixed and pipeline becomes green again. And as all the validation and verifications happening to the right side of the pipeline, it is going to take more time to fix issues as well, involving many engineers, because the failure could have been caused by any code change. This is true, especially when an issue happens in production, not only everyone has to be involved to figure out the problem, but there is going to be lot of unhappy customers and loss of revenue.

    What if you have something where pipeline blockage is not possible. What if you can can run the same set of checks you run in main pipeline but you run them against your branch itself and when you merge your PR, it is already 'production ready', what if every PR can go to production directly? what if you have a mechanism where it actually reduces production incidents ?

    Welcome to Shift Left!