Everyone is talking about automation tools like QTP,...

By Nimeshkumar Vadgama - VN

Everyone is talking about automation tools like QTP, WinRunner, LoadRunner,Silk Test, Selenium Bla Bla bla ... but Once these tools come into real practice and he\she has to automate test-case(s) with them in existing automation framework.

How far we can go with our goal?


This post gives opportunity to discuss on characteristics of test-case(s) while doing designing for test-case(s) in automation. Below are the couple of thoughts, I believe to have in automated test-case(s).

§         Concise - Test-case(s) should be as simple as possible.
i.e. Test-case(s) should not call multiple other complex Test-case(s). It should have minimum dependency.

§         Self Checking – Test-case(s) should have verification steps and It
should report in its results such that no human interpretation is
necessary. For example, I have found in one project; team has around 1500 test-case(s) – out of more than 44% test-case(s) has steps like

1.      Open Menu Item.

2.      Enter A/C number and other Inputs on screen say for A.

3.      Click on Button "Next" on screen A.

4.      Click on Button "Next" on screen B.

5.      Click on Button "Next" on screen C

6.      Click on Button "Close" on screen D – here, one product was created.

Here, all screens (A to D) have Button "Next" and "Close" and that raises some real concern to take care. Why? Because of default values of each screen are missed to verify. Test-case for each screen should have all default values' verification steps so that user\automation tool can confirm that he has achieved so and so functional flow screen while running specific scenarios. If any new screen with "Next" and "Close" button introduces in middle of screen(A-D) in new build – this will capture by automation test-case(s).

§      Repeatable – Test-case(s) can be run repeatedly without human
intervention. DDT(Data Driven Test) or test-step parameterization is one of the big benefit of automation.

§      Robust – Test-case(s) should produce same result now and forever.
Automated test-case(s) should have consistent output. It is not an easy task to achieve this characteristic. In hybrid Automation Framework, Automation team can create BO keywords to setup baseline and this keywords should be practice well enough that test-case(s) can have baseline to initialize and other test-case(s) in queue can execute regardless of previous test-case(s) passed or failed.

§      Necessary – Everything in each Test-case(s) should contribute to the specification of desired behavior. All pre-requisites should be set well – Test-case(s) should have none or minimum pre-requisites to set manually.

§      Clear – Each step in Testcase should be easy to understand.

§      Efficient – Test-case(s) run in a reasonable amount of time. It manual test-case(s) takes 100 minutes then automated test-case(s) should not take more then 50-60 minutes at the best efficiency.

§      Specific – Each failure step should point to a specific piece of broken functionality

§      Independent – Each Test-case(s) can be run by itself or in a suite
with an arbitrary set of  other tests in any order. To avoid dependency in Hybrid automation framework, automation team can develop BO keywords and add them for each test-case(s) to avoid dependency.

§      Maintainable – Automated test-case(s) should be maintained and extended with testcase management tools like TestLink, HPQC, Test Director or many other freeware tools which can easily plug with automation framework.

§      Traceable – Test-case(s) should be traceable to the requirements.

So, when we have Test-case(s) to automate – have above protocols in mind to do your tasks more effective and efficient. I would like to have more thoughts on this ; please, add your precious comments here.

Enjoy Automation / NV

Comments

Post a Comment

Popular posts from this blog

Testing Shifts with agile automation #RPA #ML

By Nimeshkumar Vadgama - VN
Image
Someone has well said ..  “To delight customers, one should continuously innovate, implement, test it, fix it, test it, release it and do all again and again.” To do so more efficiently, I would like to add Software AG Agile Tester (SAT).  It  offers various testing solutions to accelerate agile feedback loops. Currently Agile Tester (SAT) is being used in more than  52,000+ Tests by more than 21+ Product Teams . It is under Beta release for Clients. It has two major components 1.       SAT Server - Central Repository for Test Scenarios and Test artifacts. 2.       Tools 1.       SAT Client 2.       Recorder and Playback [Snapshot : #1] Developer or QA can use “Agile Tester” (SAT) to move testing process earlier in the development cycles so that We can prevent errors rather than detecting them later;  Here We shift testing activities closer to the build process and proactively test applications to uncover defects and so Product Teams (enterprise) can accommodate releases faster.
Read more

Bots and What Not !!

By Nimeshkumar Vadgama - VN
Image
These are very highly scalable Bots empowered by PaaS solution with MLOps and DevOps pipelines. To setup and make these simple deployments in your premises, We have RPA, MLOps & DevOps Tools, Frameworks and Techniques to apply for corporates. Please, feel free to contact me for further progress in your project or any consultancy.
Read more

Need > Want

By Nimeshkumar Vadgama - VN
Image
If We dont ask : Why should We implement this?  then We would miss out the best alternative solution to resolve the true needs and later on We fall under the high performance losses. I have many technical leader friends who have always thoughts and fight in their minds that when choosing features for product development milestones what is the actual "needs" for specific features to implement first on high priority; This is the tricky question and one gets the right answer in right time when He / She exercises and grows with correct set of tools and techniques and or process with his / her teams and clients. To understand the clients' and teams' NEEDs (and wants),  There is an easy simple structured process -- It is called "Design Thinking"   I use to call  2D-3D technique  and am practicing this from many years. 2D means  2D iamonds technique to initiate with teams various meetings 3D means  3D imensional approach to continuously add feedback loop in ev
Read more

Automate your everyday tedious tasks and free up time for higher-value work (with Microsoft free RPA solution)

By Nimeshkumar Vadgama - VN
Image
Automate your everyday tedious tasks and free up time for higher-value work with "Power Automate Desktop". Today, Microsoft annouced "Power Automate Desktop" free for Windows' users. It uses low-code RPA (no coding required) to give you time back by automating your repetative non-productive “busy work.” :) Image Credits: Westend61 / Getty Images Current release offers OS native automations task on Windows 10 Home, Windows 10 Pro, Windows 10 Enterprise, Windows Server 2016, or Windows Server 2019 and web based on t he Microsoft Edge (version 80 or later) or Google Chrome browser. Minimum hardware Storage: 1GB RAM: 2GB Recommended hardware Storage: 2GB RAM: 4GB .NET Framework 4.7.2 or later. Note : ARM devices are not supported. Thank you for visiting this post -- stay connected !! Source (Credits) to https://flow.microsoft.com/en-ca/blog/automate-tasks-with-power-automate-desktop-for-windows-10-no-additional-cost/ Reference : https://docs.microsoft.com/en
Read more

Respect is not earned, It is given ⚘ 🙏

By
Image
🙍🏻‍♂️   { Dev team Lead } : Sorry, We missed the deadline. 🙍🏻 { Normal Architect } :    Hey guys you have missed the dead line 3rd times,  You are the worst in the earth. 🙋 { Smart lead Architect }  to  🙍🏻 { Normal Architect } You know, This will raise dark\low energy around our teams. You should handle the situation with calm & composed way and express more empathy towards our teams; in this situation, We would aware teams by replying as  "I feel really frustrated because We have missed dead line, I am very worried about the project" "I want for you to tell me when you run in to the problem sooner so we can prevent this happening again."   --  after all respect  🙏  is never earned, It is given  ⚘ #horsemen behaviour #contempt or #stonewalling,  #culture, #devops, #mlops, #aiops, #architect, #smart-work
Read more

Popular posts from this blog

Typical Project flow with QA Loop in Jira (Atlassian)

By Nimeshkumar Vadgama - VN
Image
Last week, one of my friend needs some help to establish Project\QA workflows on Jira (Atlassian) So here I am happy to share some of my odd solution. Project Flow problems or hard to implement in Jira were * One stage splits with multiple stages in flow. * More than one stages merges to one stage. Here We have Brainstorming splits to UT - ST stage and Dev Review - QA Review merges with Review stage executed by System Group Members in project flow. One issue splits with more than one issues, can also be implemented with sub-tasks feature but it may not push next stage in the project flow as the project progresses; all sub-tasks are linked to the parent task only, may not execute inline flow; may not give more control to administrator\lead and may be more complicated to maintain. Sub-tasks may not be merged to one task on transitions after Dev. Review / QA Review merges to Review stage. Core objective is to implement flow that anyone can see each stage of the flow and can
Read more

Increase ROI in your organization with Automation Testing

By Nimeshkumar Vadgama - VN
This article offers answers for below questions with case-study Why do we need automation s/w testing in organization? What if organization does not have fund to purchase license for expensive automation tools? In simple way, we can say the core objective of automation is helping to finish any testing\QA task more accurate, easier and faster way with less risk involved for failure. Say for example Tools like # Functional automation tools QTPro, SilkTest, Canoo, Selenium, VBMacro. # Load/Stress automation tools LoadRunner, SilkPerformer. # Cookies reader tools. # HTTP request / response reader tools. # File comparison tools. # Tesecase Management Tools. # Web Page link / image finder Tools. # Broken link finder Tools. and many other tools we can categorize in automation testing fashion to make QA Process more smoother; Automation Testing also used for Repetitive testing task activities… As a human nature, manual tester can not perform repetitive tasks more accurately comparing to mach
Read more

Tip to create workflow in JIRA quickly

By Nimeshkumar Vadgama - VN
To my colleagues who want to create quickly new workflow and don't want to touch xml \ property files. On Administrator \ Workflows If you don't have default workflow then create default Workflow with default JIRA "workflow" - it will show status as "active" so we cannot update its scheme \ workflow steps. Copy this workflow -- it has status as "Inactive" so we can update workflow scheme. Go to link "steps" and add new status \ transitions for new steps as required in your workflow. On Administrator \ Workflow Schemes Create new "Workflow Scheme" then click on "Workflows" link operation of new workflow just created. Assign workflow to scheme,... Issue type "Bug" and select our workflow from the list. Assign other workflows for issue types : Task, New Feature or Improvement with default workflow ( named JIRA ) or your workflow. Now our workflow scheme is ready to associate with our project. Go to you
Read more

Headless Automation Testing

By Nimeshkumar Vadgama - VN
Image
Headless Testing means testing without GUI. There are couple of testing such as Unit testing, Component Testing, Module Testing, Integration Testing, CC (Code Coverage of Condition) Testing \ Base Path Testing, Mutation Testing, DB Testing, API Testing and or Web Service Testing may fall under Headless Testing. As you can see most of testing are white box or gray box testing. In XP\XT (Extreme Programming\Extreme Testing) of agile, It is the first step in implementing story. Open Source tools such as Watir, Warin, Junit, Nunit, HTTPUnit, HTMLUnit, WebTest Canoo, Fitness, Selenium RC and scripts like shell, vbscript, groovy, SoapUI (and some good paid tools Autoczar, QTP, SilkTest, TestComplete) are helping to automate this type of testing and play effective and efficient role in the QA feedback of product lifecyle. It actually tells us where is the issue. So, always say "Yes" to Headless Testing in your project.
Read more

QuickTest Pro and Traceability Matrix

By Nimeshkumar Vadgama - VN
Image
I like to share one automation experience or in other sense the challenge I had in automation. I joined one company as an Automation Quality Analyst Consultant. It is fast growing Company. I was as a tool smith like person recommending tools for QA team to make manual testing tasks more easier\reliable and fast way. We had established freeware tools for testcase management, defect repository and qa\project process and developed test-suites for regression and smoke testing in QTP. As we all know regression test-suite is bulky one and at that time, mine was including more then 617 testcases automated and that’s why taking more than 3 hours to finish execution. I have split test scripts on functionality vise and created test batch but the problem is test batch report does not give status for each testcases in automation execution and that encourage me to develop “TM live” tool interfaced with QTP 9.1. “TM live” means Traceability Matrix on live (parallel with automation suite execution)
Read more

AFT (Automation Framework Team) should not take developers' false catches

By Nimeshkumar Vadgama - VN
Image
What does It mean by "developers' false catches" ? It means those implementations or application unexpected behaviors which should not be automated with automation framework. Why those should not be the candidates for automation? It is observed that adding these kinds of requirements in automation may set short ROI for organizations but it never becomes for long terms – You may ask “why” again, below are couple of examples which put more lights on this question. Case-Study : #1 “Product Team has new requirements in build 1.2.x like objects inputs are changed with prefix or suffix strings and that affects more than 1000 automated test-case(s)” Due to limited resources and short dead line to certify build(1.2.x) of the product, Product lead comes to AFT and asks for help. He requests to update Automation Framework in such a way that manages prefix and suffix inputs and his team does not have to update their test-case(s). As part of the service team (AFT), we provided soluti
Read more

Testing Priciples & Vocabulary

By Nimeshkumar Vadgama - VN
The principles can be defined as 1. a rule or code of conduct; 2. a general or fundamental, law, doctrine or assumption; In software domain, these principles focus lights to test engineers on software systems, how suppose to build them and how they expect to behave. Principle #1 Testing is the process of exercising a software component using a selected set of test cases, with the intent of (a) revealing defects, (b) evaluating quality. The term “defects” used in this and in subsequent principles represents any deviations in the software that have negative impact on its functionality, performance, reliability, security and or any other of its specified quality attributes. Principle #2 When the test objective is to detect defects, then a good test case is one that has a high probability of revealing a yet undetected defect(s). The test engineer expects to work as scientist does like he creates hypotheses to prove or disprove them; that is determine if the specific defect is present or
Read more

QA Project Checklist

By Nimeshkumar Vadgama - VN
Here is I want to share qa project management checklist I used in real scenarious. Project Initiation Prepare System Test Estimates Define System Test Approach Define Testing Scope Prepare DRAFT System Test Plan Review System Test Plan Prepare Test Schedule Request Test Resources Request Business Expert Request Management Support Request Environment / Technical Support Request Facilities (Desk, Chair etc.) Setup Test Project Folder Revise Test Estimates Define Entrance / Acceptance Criteria Agree Communication Channels Agree Reporting Procedures, Methods and Frequency Define Exit Criteria Design Release Notes Template Test Preparation Agree Builds / Drops Schedule and Contents Agree Release Notes Contents and Format Agree Error Management Procedures Define System Test Roles and Responsibilities Assign Test Roles and Responsibilities Assign Test Case Preparation Primary Responsibilities Assign Test Case Preparation Secondary Responsibilities Prepare High Level Test Cases Prepare Low Lev
Read more

How to automate test-scenarios which have Java Objects built on JMesa , JQuery, JSON and AJAX technology.

By Nimeshkumar Vadgama - VN
I had a challenging project to automate Java Objects on the fly – sharing some part of it. Challenges I faced 1. Objects which are built on top of JMesa , JQuery, JSON and AJAX technology -- are not recognized by professional automation tools (such as QTP and SilkTest). 2. How to automate Dynamic Graphs which are implemented with technologies like Flotr and 3D Canvas. 3. Web application needs to automate with cross-browsers ( IE 6.0+ , FF 2.0+ or Safari 2.0+ ) It focus objects screen rendering issues which are different from one browser to other. How can we overcame • Challenge #1 and #2 can be resolved with below automation approach. Verify HTTP Responses when user does some actions like objects fire specific AJAX calls; We simulate these AJAX calls ( HTTP requests ), capture valid\expected response, set them as baseline and in QA loop we simulate user actions again with automation, capture actual response and compare with baseline. • Challenge #3 can be resolved with below automatio
Read more