Everyone is talking about test automation these days without actually realizing the real need for it. By “real”, what I meant here is: first, we should analyze whether we really need automation for a given project or not? Do we have skilled resources to work on the project? Do we have the required tools/technologies and most important is the budget estimation in place? Does implementing an automation framework bring ROI to the organization? Some organizations are targeting to achieve 100% automation which does not look convincing to me. To achieve 100% automation is a pure myth. You will need some % of (manual) testing along with automation in order to deliver a successful project.
2)When it comes to testing automation, what has to be done to make sure that it’s effective?
Based upon my experience and knowledge of test automation, here are few tips on how to make it more effective:
3) Do you think working from home is a safe option considering the vulnerability of computers and networks we use for our domestic purposes?
Since the Govt. has declared the norm of Working from home, we are more prone to cyber-attacks. As an experienced professional, one must understand the security and vulnerability of computer system and network devices.
We should be taking precautionary measures in order to prevent a security breach. When we are working from home, the probability of getting the system attack/data breach/data decryption/data security is at its peak so one must be attentive to avoid such a threat.
So, we should use personal computers to do personal work rather than company’s devices. A basic level of security can be achieved with small steps in a day to day life.
4) what are the challenges you face when it comes to test automation?
5) What’s the difference between a good test and a bad test?
A good test should be reliable, easy to understand, crisp, and independent from each other. Good tests always add value to a project. Good tests can be automated considering the qualities of the test. Good tests are a result of critical thinking and deep analysis of a given user requirement.
Whereas Bad test which consumes a lot of time but does not provide any value to a project. These are unnecessary lengthy steps and can’t be automated. This does not convey the purpose of the test. Not understandable and not readable as well.