Get started with test automation

Automating test cases is beneficial but if not done right can prove effort draining exercise for team. Before getting started with test automation its necessary to analyse the requirement for it and then decide on approach.

Most of the times, test teams jump into automation and then end up doing manual testing as automation requires more time or framework is in broken stage or lack of understanding on framework as one who developed it as already move on to another team. So, it’s vital to analyse and have an approach that gives team best out of their test automation.

So first let’s see what automation is. Test automation is like testing the software with another software. So basically we are building software which can be called as testing tool or test automation framework platforms and maintaining them.

Identify Tests:

Test automation gives major value in avoiding repetitive manual testing. So, first need is to identify tests that are required to run before every new update in app. Also, not every test case should be automated. Some test cases might be tricky to automate and maintain automation around them. We need to analyse time required To automate and value out of it. Some test cases do give better confidence if tested By human intelligence. So considering all this, firstly we need to come up with test automation suite.

Get right tools:

Look out for right tools to automate your tests. In today’s agile methodology, time in building new things can easily be avoided by re-using existing tools in market. There are lot of tools in market, which can be open source, freeware or licensed that help test automation. Specially in functional test cases there is more scope in going for tooling option.

Decide automation approach:

Every team needs are different. We need to decide on who writes automation, when tests are automated, who/how/when to run them. There are few popular approaches here like TDD – Test Driven Development or BDD – Behavior driven development. You can always analyze few example case studies in it and then come up with approach (may be more customized to your team) that best suits your team.

Select language:

If you plan to develop test automation framework, the first step in it will be which language you will select. Few aspects while selecting language will avoid hurdles later on. Select the same language that your app is developed in. This will avoid team to have learning dependency of another language. If there’s no easy automation approach in that language, then prefer to choose language that’s popular in market, free to use, has free IDE’s available and has tremendous help out on web. Few of such examples are Java, JavaScript, Ruby and Python. This will help to get more help on web, during automation and also later new person coming to team should more probably have skills in that language.

Run platform:

To run your test automation, it will require some platforms like fore web apps, OS and browser are the platforms to run automation. You need to decide on which platforms you want to run your test automation. There are some cloud platform services available in market which will provide you required platforms for test automation in cloud. If your platform requirements are heavy, it’s preferred to use cloud based services instead of you investing efforts and cost in building these platforms and maintaining them.

Document analysis:

Though documentation is considered dead activity in today’s time oriented development, we must brief about our analysis and plan for test automation. This documentation can be very brief and must be meant for any new person in team to understand our objective and approach in test automation. In our next blog we will cover building automation framework, in which we will discuss more on language and platforms for automation.

27, January - 2022

Try it now for Free