Test Automation: Who Should Construct and Who Should Implement?Testinium
Selenium library has a story of 15 years. This idea first emerged in Chicago, when Jason Huggins laid the foundation of Selenium as a “Time and Expenses” application at Thoughtworks company in 2004. Some experiments may have been done before; but the idea of automating software testing has become so easy to implement for the first time.
About 15 years ago, mobile technologies were developing rapidly, but it was still quite primitive. It was only a few years later that as a result of the peak in mobile phone sales and technology migration, mobile technologies became the new focus point. This way, mobile technologies became a new norm while they were shaping into their present state. Millions of new projects have been developed which were compatible with the predominant IOS & Android operating systems. Considering the demands that were noticed during the innovation of mobile technology; quality and speed have become decisive factors in the competition for projects that were compatible with mobile operating systems.
Considering all approaches to automation of software testing, Record & Play and Image Processing methods, no matter how great, were constantly generating maintenance costs and holding the risk of not working steadily. It would not have been a wrong approach to say that it could lead to an amount of loss that would not be preferable at any case.
Test automation technologies began to provide services to reach at the requested quality faster. But these technologies have brought together methods with certain rules which required a discipline at the prototype level of a software project in order to create a scenario. Product Owners, Analysts, Functional Testers back in the day were responsible for the quality of software, and therefore had no related experience.
Who would be responsible for applying these new methods and quality? It would be obviously a dream to expect these developments from the already existing developer team. They themselves were already struggling to improve quality by writing unit tests. The tight schedule of the developer team, which also included full of development at the same time, would never suit this. It was obvious that a whole new team had to be created for these developments.
As a result of such developments over the past years, the BDD concept has begun to take place in companies and therefore in people’s lives. In 2014, Cucumber entered the lives of the teams who were responsible for quality. Then different libraries began to emerge to provide the same benefit to the same group. One of them was Gauge.
If you’re a startup, even leaving the test automation aside, it will not take much time for you to realize that you do not have a large budget that can cover the expenses of even a QA person who can run a manual test. In this case, the only QA worker you can rely on is, of course, the Product Owner on your team. This person who is dominant in all aspects of the business and who leads the developments by making analysis will also be responsible for the quality at the same time.
What if you were a manager at a bank or an e-commerce company? Although these sectors are different from each other, they are similar in levels of quality and actually this conclusion applies to all B2C running companies. If you are looking for a position in these companies that is in charge or should be in charge of quality, even if they are continuing their business development with different methodologies, then analysts who own various catalogs or modules are what you are looking for.
You need to make certain preparations in order for automation scripts and products to be created by people truly responsible for quality. Firstly, the people who are responsible from quality need to do automation analysis work with domain/product information. Following this, the immediate task is to determine the correct keywords. As the final step, you need to have the infrastructure built by selected people from technical staff. This preparation work can be done with about 20 keywords for a startup and the duration would not exceed 2 weeks. Of course, you would need about 50 key words in a much larger company like a bank and the process generally takes less than 2 months. After you are done with these steps, all preparations would be complete.
Automation scenarios have become easily applicable in the language of software with the support of libraries such as Cucumber, Specflow, Gauge.
What do you need to do to run these scenarios? Don’t be afraid, you will not need technical skills for this either.
By signing up for a free account on our product Testinium, you can instantly run your script on hundreds of different browsers and on real mobile devices, review reports and use your time more efficiently.
It’s time to BDD.