Terminal time, I talk about how team setup and how it should touch your test scheme. This week, I want to extend testing frameworks.

Let ’ s offset at the beginning and mouth about what a testing framework is and why you should feature one. In short, a framework isn ’ t just one thing. It ’ s a coupling of different things—guidelines, coding standards, good praxis, instrument and libraries—that work together to make us faster and more efficient. An effective test framework can lour upkeep costs, improve codification reusability, help us center on writing tests instead of writing boilerplate code before coding tests, and more. The point is that a single/library instrument will hardly extend all my testing demand, but putting together a few testing tool and libraries that work in harmoniousness will help me get there. When I say “ framework, ” that ’ s what I ’ m verbalise about.

From my perspective, there are three reasons to use a framework:

• Reduce maintenance costs- a framework simplifies sharing common functionality that ’ s needed across the team.

• Be faster- we can make changes by only changing thing in one place when we feature a individual examination framework.

• Be responsive- we can bootstrap code to publish tryout, and this is embed in the model. When we are creating new test cases, we can get to implementation much quicker.

What features should your framework experience?

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

I create a list (see image below) of things an efficient examination fabric should do. This is entail as a guideline, not necessarily a set blueprint—and there may be additional things to consider give your individual situation.

It ’ s also crucial that you take into account whether the framework you ’ re considering is future-ready. Does it change and adapt to trends, which will enable you to evolve appropriately? For illustration, will it let the dev team to switch JavaScript framework? Consider this scenario. If your web app is written in Angular, but the team determine for some reason to change it to React, will your framework allow you to start quiz the React app without too much additional work? Another good example why you need a “ future ready ” framework could be a situation where the squad depart out only needing to indite tests for a web coating, but after some time has surpass, they develop a mobile app that needs to be tested via Appium as easily. An effective examination model should be capable to support/leverage the squad to indite tests for the mobile app without the need of going through all the hassle of place everything up from shekels.

How do I build my testing framework?

Two words: open source. “ But Diego, ” you may say, “ Why should I use open source tool to create a test framework? ” Simply put, it ’ s because you don ’ t demand to reinvent the wheel! You may think you ’ re the solitary soul who has encountered a particular testing trouble, but I secure you that isn ’ t true. Many other people have likely experienced the like issue and get created and shared open seed tools and resources in the community that can solve your challenge.

So how do we choose open source tools? First, you ’ ll be direct by the programming words you ’ re using. Also, assure GitHub to see how many stars and forks, as easily as how combat-ready the project is. Are citizenry replying and do the community appear combat-ready? Is thither solid documentation? Often when a project fails, it ’ s because it lacks good support. Conversely, good documentation can really help you get started easily.

Also, choosing an exposed source tool should really be an effort of the total team. Everyone should be involved place in their own concepts and ideas. First do you your enquiry, and then do a proof of concept. Try out an exposed source instrument with your team to determine if it ’ s a good fit for you.

If you enjoyed this post (part 3 in a series), check out the former installments of Diego ’ s “ 5 Steps to Jumpstart Test Automation ” series:

• Part 1: 

• Part 2:

• Part 4:

• Part 5: