Tesbo is different than Cucumber, SpecFlow and Other BDD based Tools.

Cucumber Dec 19, 2019

Recently we have released the Tesbo for the public and started to post on the social media with the small Introduction like

Tesbo is a hybrid test framework which allows you to write the Test in the simple English language"

as soon as I state this, Most of the Test Engineers have one question in mind that seems like the cucumber is also providing similar features than how is different from the cucumber?

In this article, we will discuss the Main difference between Cucumber and Tesbo.

Cucumber follows the BDD Approach which allows the user to write the Test in the Natural English Language called Gherkin and this text need to map with the code snippet to run the Test like here

Feature File : Cucumber

See here, First you need to write the Test into the Simple English language and then you have to map with the code like this way.

Mapped Code File : Cucumber
Mapped code file. 

This increases the overhead on the Test engineer to maintain the feature file plus mapped code when something has changed. On the Initial level, It goes easy and gives a clear picture of the project but in the long term, it makes it hard for the engineer to maintain everything on daily basis and finding new bugs from Application.

While in Tesbo, which also allows you to write test into the plain English language, but you don't require to map with code as it is based on the keyword-driven, It's internal algorithm will understand the meaning and perform an action based on it. here is the example

Test File : Tesbo

Seems Interesting!!! Right ??

No code at all, Just write the step and it's ready to run. Tesbo has all the most of the Selenium command and common features that require in day to day Tester's life.  However in some situation, if you feel you need to write a code to meet your requirement you can do it as well, same way as Cucumber !!!! ;)