How the Repository Driven Test Automation (RDTA) will make test automation more efficient, easier & maintainable

Many testing organizations find themselves lagging behind the development forces on the agile journey; it is obvious for us to demand an easy integration between all software program elements developed. Do we treat our testing artifacts in the same manner? It is time to make the change. Take this opportunity and prepare a right testing infrastructure that will enable you to reuse and integrate all testing artifacts as basic components for the same puzzle. Make test automation to integrate and operate in similar manner. Mobile emerging world present this issue even harder - the versatile and speedy continues integration required to multiply our demand for reuse and efficiency. Proposing reuse of testing artifacts as a fundamental principle for the creation test automation is what makes RDTA a unique approach to the buildup process of test automation infrastructure. Having your attention aimed to the question; what will be done with your efforts later on and how someone else can benefit from your previous efforts? Drove us to the new concept for forming test automation. The term software repository here refers to a storage location from which software packages or artifacts may be retrieved to be reuse on another system or other software products. This tutorial explores different aspect of software test automation artifacts reuse and elaborate several practical implication and changes implied from the new paradigm to be implemented in a software development organization. Report about an empirical case study of implementation of RDTA in a large organization will conclude this tutorial, presenting the benefits and some of the obstacles facing this approach. RDTA approach is yet to be matures and elaborated, this tutorial will present several new subject needed to be formally theoretically modeled and addressed