Understanding Tesbo structure

In the previous article, we already have seen the Tesbo is not just a normal tool but it’s a tool that you imagined in your life for automation. Definitely, you’re excited for the implement Tesbo in your system, so why wait Let’s go and do that!

Tesbo in beta!

Yes, Tesbo currently is in its beta version, You can register for Tesbo beta from below link.

Register for Tesbo beta!

Before moving forward you’ll need a few things installed in your system

  • Pre-Requisites
    • Java
    • Maven
  • Getting Started 
    • First of all, you’ll need Tesbo jar for your project which you can get from registering here.
    • Tesbo is defined its own template for the setting up the project if you need you can download the Tesbo template skeleton from here or you can follow the steps below to design by yourself as well.
  • File Structure:
    └── src
    │   ├── tests
    │        ├── Runner
    │        │      └───
    │        ├── locator
    │        │      └─── moduelName.json
    │        └── suites
    │               └─── moduleName.suite
    └── config.json 

Now let’s understand get the idea about each and every file from the Tesbo Skeleton Template.

  • tests package

tests package is default package comes with your maven project template, this tests package contains all the Tesbo test suites and locators files.


TestRunner is the main Test Runner invocation class provide by Tesbo itself. You don’t need to work on this class, you need to create a Runner class and pass the default Tesbo code snippet to initialize the Tesbo run.

  • Locator Package

As you can see in the above skeleton, Locator package contains JSON files, These JSON files are used to define the locators for your project. You can pass as many as locators in a single file and also can create multiple locators file as per your modules.

  • Suite Package

Suite package contains all the suite file where your Test Scripts are defined. You need to write your test scripts in this suite files and Tesbo will work for it. In a suite file, you can define as many as you need tests as well as you can also create multiple suite files for the multiple modules.

Note: The name of the suite files (.suite) and locator files (.json) should be the same for the modules. i.e If you’re creating a suite file for Login as login.suite then you need to define locator file as login.json for login.suite file.

  • config.json

config.json is used to provide properties for your test execution like, in which URL you want to execute your suite, which tags from you need to execute the tests, the browser supports, grid supports and many more.

Let’s look more in-depth about this Tesbo file structure and its files in the next article.

#Step2QA #Tesbo #AutomationFramework

  • Facebook
  • Twitter
  • Google+
  • Linkedin
  • Pinterest

Leave a Comment

Your email address will not be published. Required fields are marked *

It is main inner container footer text