Many organizations treat automation as a buzzword and consider the segment as white elephant. They are not all wrong, automation in the initial days yielded lower ROI than expected. Gone those days when automation used to be an selling point of any organization. Now a days automation is the must have feature of any organization to streamline their speedy delivery.
Should robotize the testing work? General reasoning about mechanization is that it is handled to record and play it back. The greater part of the computerization depends on organize based testing. Computerization is about record once and runs on numerous occasions.
Result !!!! less time for computerization.
But these individuals disregard the progression of Automation innovation. Mechanization isn’t about record and playback. There are a few different parameters should be dealt with. Till what level computerization ought to be finished? Do you have adequate and talented assets for Automation? Is time reasonable for computerizing the experiments?
There are situations when useful individuals give general cases to the automation group for regression testing.Having said that regularly changing necessities including User Interfaces, Business functionalities, and business condition are the practicality issue with Test Automation.
Test automation faces its own issues other than functional related issue which adds Challenges in Testing(DevOps Testing issues or Software Testing challenges).
People’s perception about Automation Testing-Automated Testing challenges
Some managers thinks automation is an additional task just like testing a flow.And this can be done by manual resource only.Since they have procured an expensive tool,it is just a matter of record and playback. It is very easy and quick.
In reality it is the biggest myth about automation testing. Automation testers are the special group of people who needs to know coding,tool and system. They will also have a creative destruction mind. They know the design of an effective framework that actually simplify the testing process.
Similarly the second myth in this space is that it is easy for a developer to pick up automation testing and finish. It is somewhat true but not completely. They know coding,system but they make lack in tool and tester’s mentality.
So this wrong perception will also create issue in testing and adds challenges in Testing as well as Automated Testing challenges(DevOps Testing issues or Software Testing challenges).
Do automated testing tools make testing easier?
Indeed and no. For bigger projects, or continuous long haul ventures, they can be profitable. Be that as it may, for little projects, the time expected to learn , create and execute them is generally not beneficial. A typical sort of computerized instrument is the record/playback type.
For instance, a test engineer navigates all blends of menu decisions, exchange box decisions, catches, and so forth in a GUI and has a computerized testing device record and log the outcomes.
The account is normally as content, in view of a scripting language that the testing apparatus can translate.On the off chance that a change is made (for example new catches are included, or some hidden code in the application is changed), the application is then re-tried by simply playing back the recorded activities and contrasted with the logged outcomes so as to check impacts of the change.
One issue with such instruments is that if there are constant changes to the item being tried, the accounts must be changed so regularly that it turns into a very tedious assignment to ceaselessly refresh the contents.
Another issue with such apparatuses is the translation of the outcomes (screens, information, logs, and so forth.) that can be a tedious undertaking.
For these reasons, only procuring automation tool will not help test team rather adds challenges in Testing as well as Automated Testing challenges(DevOps Testing issues or Software Testing challenges).
How to resolve?
With the upgradation of technology , automation is no more a luxuary item.It is more than a necessity now.We need to use automation to test unmonitored or unmanned manner in test execution. W need to use smoke and regression testing technique before taking up a build for manual testing.
We need to remember that automation testing is :
If we can apply automation in proper way, it will reduce the turn around time and provides greater ROI.
No support for POC-Frequently faced challenges in automation
In a nutshell no POC creates Challenges in Testing.To uptake a tool, we need to do POCs(proof of concepts) on multiple possible flows. These flows needs to be identified before hand. We lag to identify the flows and it is seen that we heavily dependent on tool vendors to automate flows. Tool vendors on the other hand always choose some flows and automate. POCs from vendor looks so easy that we tend to buy that tool.
When I looked back and checked one of our previous decision, I realized we have not set up a dedicated team who can perform this task. The existing team , part from their regular deliverables , were given a task to evaluate a tool. Guess what happened next, they picked up some random flows which they felt they can complete within the time boundary. Then they discussed with the vendor to automate them. In this process we all skipped the important areas where we need major tool support.
So lack of understanding and knowledge about a tool is a major factor on deciding and finalizing an upcoming tool. Testers rely on an old known tool for upcoming testing.(Testers personal bag and baggage).
On the other hand management needs to understand noting comes free or there is nothing called a free lunch. To get a good tool,they have to acquire it.
Lastly even we have procured a tool, we saw the tool failed during production support. One major reason what we found out was that we never educated the testers on the new tool. That caused an unwelcome behavior from testing team towards the tool.
So once we procure a tool, we need to educate the test team. We need to engage testers with the tool.There should be a constant effort to engage testers with new tool. They can produce demos in regular interval.