Accelerate Test Automation

In this white paper a comparison shown between a traditional approach followed in test automation in any enterprise with SimplifyQA platform recommend approach. 

Traditional approach 

Typically in organization project team the approach followed for test automation is 

  • Understand product architecture
  • Understand product environment UI, Middleware, Backend
  • Identify testcases to automate 
  • Evaluate and narrow down on tools 
  • Decide on framework attributes

In order to keep easy maintainability for scripts developed by team a decision will be taken on automation framework to be adapted. There will be planned effort to create this framework before allocating test automation tasks to team. It takes few weeks time before everyone stops blaming framework for their delayed delivery of automated scripts. Though we start with some focus like keyword driven & data driven we all land up in hybrid framework! You may hardly see anyone we are not following hybrid framework finally. 

Some key pain points in this approach are uncontrolled duplication of object names, duplication of methods, major merge issues delaying release of automation scripts for team use. Many times you see that framework itself evolves with focus on data driven, keyword driven and modular and slowly stops all merge issues overtime. Hence we need several weeks to say “complain on automation framework reduced”. However at any point if script fails in execution not traced to product issue will be blamed on framework again. Automation architect will find a quick fix and we move on.

You may also see the focus may be divided into phases in order to appraise stakeholders on ROI for the investment done and get additional budget for subsequent phases.

Phase 1: Frontend automation on web Phase

2: API & DB level testcases

Phase 3: Frontend automation on mobile devices (if part of environment supported)

Phase 4: Organize the automation assets to achieve staged level testing to go till regression testing

But what management hates to hear is “in that environment our automated test will not work”. QA Manager has to fight a lot for budget approval for taking automation journey forward. Our experience shows a frustrated QA Manager will be looking for a magical solution to all challenges he/she is facing on the field. 

SimplifyQA platform based approach

In this approach many of the challenges shared above are addressed with unique features in the platform.

Write testcase once

In this platform there is no need for you to write testcase, execute manually and pass it on to automation team. What does this mean!? Testcase creation is made so simple with easy to use UI. Even a person without knowing any scripting language can create automated test scripts just by following a disciplined approach of writing testcases and saving. All he has to understand the place where UI object names are stored, what actions required on UI object, any parameter which supplies data to testcase in that step.

All we need to do is capture UI object properties into project at page level and maintain using Simplify3X provided browser add-on. 

Built-in framework

The platform with test data creation and maintenance as separate feature supports data driven approach. With validation of duplicate objects creation and function creation using tested scripts modularity is brought into team output. Built-in functionality provided in platform to manage synchronization issues while executing scripts for any slow rendering issue of object.  

Testcase versioning

This is a unique feature which supports continuation of automated testing at every stage during functionality development and evolution. We can select which version to be used at the time of execution so that you have automated test modified and old both working at any point of time. 

One platform for web, mobile app

SimplifyQA supports test automation of application in web as well as mobile (android & iOS). This also supports test automation at THREE layers UI, API and DB. 

Cloud Execution

With options to execute testcases on cloud during run time you can have parallel tests triggered with more test environments covered in shortest time. As you achieve more in shorter time the various phases we discussed in traditional approach is advanced in time line making stakeholder extremely happy on ROI for test automation effort. This optimization saves time and cost significantly.

Summary

In the new approach we eliminate framework development & stabilization effort, one time test creation saves manual testcase creation effort, automation testcase creation helps anyone to contribute in test automation if they understand application, testcase versioning helps multi stage test automation coverage, one platform helps reuse of automation effort, cloud execution increases productivity of testing team.