Abstract

Software professionals employ the disciple of Test automation to create test scripts that validate the technical and functional aspects of a software. A well known test automation model has been defined in the technical literature as, test automation pyramid and is widely referenced when it comes to automated testing within Agile methodologies. Test automation pyramid implies that the interaction with the system under tests should be made on 3 layers, Unit, Service and User Interface. Other interpretations of the model also suggest a quantitative approach, in which the larger surface implies more effort invested in that layer. This paper analyses 5 software projects, developed under Agile principles in which test automation is an important aspect of maintaining high quality standards. The data analysis will focus on the numbers of unit, integration and user interface tests and determines whether the findings comply with the theoretical model. The conclusions attributed to this paper suggests software professionals involved in the development of test automation should put more critical thinking in the models promoted by literature. Also, the paper identified a need for alternative models that are consistent with industry best practices and better correlated with information from real life projects.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call