Why automated testing?
Himanshu Tewari
Sr. Product Manager at 91mobiles (ex-SaaSworthy, Prospecta) | PM from ISB | CSPO? | Growth Hacking | Travel Vlogger
When I entered in the QA/QC(Testing) field my seniors gave me some excel files which were some test cases and I was asked to execute them. after some time I started writing my own test cases and understood how to create scenarios and write good test cases. I know it's not about automated testing, but automation testing is also coming out from manual testing.
The main role of automation testing is reducing the manual effort in the time of regression testing. Nowadays the organizations are looking for a guy who can play both roles. he can create the scenario and after testing, he also can automate those scenarios. if you are starting your career as a manual tester I would like to recommend you to learn automation testing also.
When Does Test Automation Make Sense?
- When there are many constant test cases execute by manual tester
- When we have a large number of test suite
- When we need frequent test result of regression testing
- When we have a certain amount of time to finish our testing
- When we have to reduce the cost of expenses
Many tools are available in the market for automation some of are paid like QTP and some of are open source like Selenium web driver.
If you know any of the programming languages like JAVA, PYTHON, PHP,RUBY etc. So it's very easy for you to learn Selenium even you can develop your own framework with the help of selenium libraries.
I would say you should start with selenium because it's easy to understand.
Co-Founder@Digi Acai - SEO Agency for D2C Brands
8 年Good Job. Himanshu :)
Head of Applications & Data | Data Science | Business Strategy & Value Focused
8 年There is no such thing as automated testing. Testing is a performance. A person who writes code to check the output of an algorithm is a developer. To much emphasis is put on this so called automation testing which is driven by the lack of knowledge of what testers actually do. I agree these automated test are helpful in regression of simple factual tasks but it's not testing.
Scrum Master/Agile coach at Retired leisure
8 年First, thanks for writing the article. However, I have a couple of comments: 1. Is the main goal of automation to reduce manual effort in regression? For me, the main goal of automation is a faster feedback loop. 2. Does automation really only make sense in the cases you've listed? I hate to generalize, so I won't, but for me, the answer to the question: "When do you automate tests" is "Almost always. And as early as possible". 3. If you're familiar with the test pyramid, do you think starting with tools like Selenium is the right thing to do?
Handcuffing automated testing to manual test is a mistake. It ignores the testing pyramid. Having automation testers do enhanced unit testing leads to an architectural understanding of the system. Then there's the system level testing with tools like Rest Assured or you can write coded web tests in Visual Studio. UI testing should be the smallest component of your automated testing framework. The limitation of Selenium is that it's only good for browser based testing. Coded UI is good for Windows based testing. QTP/UFT is an obsolete tool. If your team is still using QTP/UFT convince them to convert to something more modern and with an object-oriented language to write tests.