What's new

Welcome to adpde | Welcome My Forum

Join us now to get access to all our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, and so, so much more. It's also quick and totally free, so what are you waiting for?

Bridging the Hole Between Handbook and Automated Testing


Staff member
Mar 22, 2024
Reaction score
There are some testers who say there’s no such factor as guide and automatic testing.

Whereas I wouldn’t go to that excessive, I do really feel that pondering simply when it comes to “guide” and “automated” testing can typically make your testing technique really feel disconnected and siloed.

Nevertheless, pondering extra holistically and aligning these two testing approaches is crucial for guaranteeing constant performance and a high-quality product.


I not too long ago spoke with Javier Alejandro Re, CEO of Crowdar and Founding father of Lippia.io. about this very idea, and I’d wish to share his insights on how you can harmonize guide and automatic testing for higher effectivity.

Testing Correlation​

One of many key challenges Javier highlights is sustaining a correlation between the check situations executed by the guide QA group and what will get automated.

Because the guide testers add new situations, the automation must be up to date accordingly, and vice versa. Good communication between groups makes this attainable, however it may be tough to maintain that synchronization clear and clean when utilizing completely different codecs and instruments.

That is the place Conduct-Pushed Improvement (BDD) and the Gherkin language come into play.

Why use BDD for Testing?​

Gherkin supplies a pure language format utilizing key phrases like Given, When, and Then to explain the conduct of the system. By writing check situations in Gherkin, the entire group—
together with product house owners, builders, and testers—can use a standard language to debate necessities and anticipated performance.

Javier has discovered that when his group makes use of Gherkin to automate checks, they will simply re-use those self same situations to manually replicate and troubleshoot points. This realization led to writing Gherkin from the start of the testing course of, no matter whether or not the checks would finally be automated or not.

Man Vs AI Robots

Why BDD could be Difficult.​

Nevertheless, getting guide testers accustomed to utilizing a growth setting or code repository was a problem.

To handle this, Javier and his group at Crowdar created a instrument known as Lippia to make it simpler for testers to keep up a single supply of reality for check situations.

Lippia connects to the code repository, collects all of the Gherkin characteristic information, and permits them for use like common guide check instances.

Fairly cool, proper?

Testers can report move/fail statuses, whereas automated check outcomes may also be injected into the identical platform by way of an API. This permits combining guide and automatic check outcomes right into a single dashboard, even throughout groups utilizing completely different languages and frameworks for his or her automation.

Don’t Use Vendor Lock-in Testing Options​

A key advantage of Lippia is that it isn’t a vendor lock-in answer.

The Gherkin characteristic information reside within the code repository, so groups can proceed utilizing them even when they change to a distinct platform sooner or later. The check situations are handled as property, identical to the appliance code.

When requested about Lippia’s future roadmap, Javier highlighted plans to additional enhance usability for testers, incorporate an open-source framework to put in writing Gherkin checks for APIs with out coding, and construct adapters for clean integration with numerous CI/CD and automation instruments.

The API testing framework is already out there on GitHub.

What else does the answer embrace?

Try Lippia​

There are two primary items that make up Lippia.

One is the Lippia Framework and the opposite is the Check Supervisor.

The Lippia Framework is an all-in-one framework on GitHub that will let you automate any kind of app. Any what’s nice about it’s that it’s primarily based on a set of the preferred Open Supply parts to permit you extra freedom. For instance, they’ve adaptors for instruments like Cucumber, Karate, Playwright, Serenity, Cypress and extra.

Additionally they have the Check Supervisor piece that was developed to be an all-in-one platform to handle all of your automated and useful testing. That is one space I see many groups struggling in having a real image of all their testing efforts multi function place.

Watch this fast demo to see each items in motion.

As you possibly can see, it truly is a set of instruments designed that will help you speed up your software program testing

For groups serious about getting began with Lippia, Javier recommends visiting lippia.io to request a demo or trial.

However extra importantly, he advises trying on the larger image of BDD, not simply as an automation answer, however as a course of for higher growth that advantages the entire group.

By utilizing a shared language to explain conduct, software program could be higher documented, examined, and developed in a collaborative method.

Is BDD for Testing Nonetheless Related?​

Adopting BDD practices and instruments like Lippia requires a mindset shift and will really feel like extra overhead at first. However the long-term advantages of aligning round a standard framework for describing and verifying anticipated conduct are effectively well worth the effort.

As Javier places it, Gherkin and BDD are finally “ mixture of a instrument for the entire group, not only for the testers.”

And since BDD is all about communication it can by no means exit of favor when completed accurately.

Test it out for your self now and let me know what you suppose within the feedback under.

Attempt Lippia.io. for 30 Days for FREE​
Top Bottom