Guide to implement Proof of Concept in Automation Testing

July 1, 2016

---

Introduction :

Automation testing is the method of executing test cases using a tool. There are various kinds of automation tools available for testing a software product. Automation Testing eases the entire process of testing. Few key points should be adhered to, while performing automation testing, like the length of time to be invested in a project, how stable an application is, will automation suit the company's financial terms. These are the few points to be taken into consideration while performing automation testing.

An automation testing typically involves the following phases :

• Preparing a feasibility analysis study
• selection of the right automation tool
• choose the appropriate framework for carrying out the test
• Building proof of concept
• Finally develop, execute the test script and analyse the result.

Building Proof of Concept :

This is basically answering the many questions like what do we need to prove about our deeds like what we are doing and what shall be the outcome of the performed tasks. The term proof of concept can be thought of as a document or a demo piece of code. It describes some key areas.

Some of the key points included in a POC (Proof of Concept) document are as follows :

• The type of project we are automating . It can be a mobile, web or a desktop application.
• What all testing tasks are being performed should also be mentioned in the document.
• Allocating the budget. It is very essential to analyse whether the company is able to go for automation testing and which tool they are looking forward to approach.

Implementing POC in Automation testing requires creation of prototype to showcase it's real time usage. Hence , once the appropriate tool has been chosen for automation testing, a necessary prototype is created to present to the management team, as to how things are going to proceed. This involves the following series of steps :

• Appropriate test cases to be used in the POC should be decided .
• Throw light on the difference between manual and automation testing.
• Highlight areas that will be of some interest to the clients.
• Stressing on those test cases which shall help in focusing on the error prone areas.
• It is also very necessary to find out the areas where automation can be applied and where it can't.
• If automation is possible across various platforms.

Type of results obtained from POC :

The review of the POC document reflects that the automation tool meets the requirements of the project or not, whether it is in terms of expense that is going to be incurred on the project,the necessary resources available etc. If any deviations arise while making such comparisons, then necessary action needs to be taken.

The next phase of POC takes us to implementation of a pilot project using that tool. A pilot project means a preliminary analysis of a project in a small scale.

Implementing Pilot Project :

• Measuring the feasibility of carrying out the test cases using the chosen tool.
• Choosing guidelines to be set for the specific application tool under review.
• Choosing test cases for the pilot project implementation.
• Developing an integrated framework for automation. This includes creating a suitable environment for coupling together various components that needs to perform in tandem.
• Execution of the test cases
• Finding errors if any and report it.

Presentation Phase :

When the pilot project is analysed and reviewed carefully,it is time for presenting to the prospective clients.

• Explaining the challenges faced while conducting testing for the project.
• The basis for selection of the already chosen tool.
• Highlighting how the automation tool serves the purpose of testing requirements.
• Elucidating the test report to the clients, also the failed test cases and stating appropriate reasons for the same.

Conclusion :

We can summarise this topic by saying that proof of concept is an imperative part of automation testing process. It lays out the niceties involved in successful accomplishment of an automated software testing, thus delivering a robust end product. In this section we have primarily driven our focus on automation testing, however the same holds true for manual testing as well. Documentation of anything forms the blueprint of a project which strengthens the foundation upon which our entire software system(project) is built.