img

Introduction to Tesbo Suite

After Runners and Locators, the third and most important part of the Tesbo is Suite. 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. Also, you need to pass the Suite file name same as per the respective locators of that suites. For example, for the Login module, you can create login.suite file and also for same you also should have login.json file in the locator package. Let’s see some of the default suite keywords from which we can define test and steps in the suite file.
  • SuiteName
While running with the multiple suites, it always needs that you can identify which suite you have run or from which suite particular test is running, for that first of all you’ll need to define the suite name, which you can write with keyword SuiteName:

SuiteName : <suitename>
i.e.
SuiteName: Login and Registration Suite

  • Test
Each and every suite will many tests in it and Test is defined with keyword Test in our suite file. You need to pass the test name after defining it with Test keyword as below.

Test: <testname>
i.e.
Test: User can log in successfully

  • Test Steps
As working with the Test, you always require to pass the test steps to, in Tesbo you can pass the steps in your .suite file with Step: keyword.

Step: <test step>
i.e.
Step: Enter 'Step2QA' in @txtName

  • Tags
Tesbo also supporting the Tags in .suite file, Tags are useful when you want to run the selected bunch of test scenarios only. For example, if you need to run the Regression Tests from the suite, you can pass #regression tag for all the Regression Test script and when you’ll assign Tag to your config file, it’ll run only test with #regression tag from the suites. Similar like if you’ve Tag #smoke and when you pass #smoke in the config I’ll only run the Smoke testing scenario.

Test: Verify Login With the valid credential
#Login                // <-- Tag
Step: Enter 'username' in @txtUserName
Step: Enter 'pwd@123' in @txtPassword
Step: Click on @btnLogin Button
End

  • Collection
As one of the key features of Tesbo is that it can have reusability of codes too, it’s one of the advantages of using the Collection in Tesbo. You can define a Test or Steps as Collection and can reuse it by only naming it in the later test. For example Login. Basically, Collection is defined with two keywords, first is to define the Collection which is ‘Collection Name:’ and to call that collection you need to pass keyword ‘Collection:’

Test: Verify Login With the valid credential
#Login
Collection Name: Login to Amazon
Step: Enter 'username' in @txtUserName
Step: Enter 'pwd@123' in @txtPassword
Step: Click on @btnLogin Button
End

Test: Search and open a product
#Login
Collection: Login to Amazon
Step: Enter 'iPhone X' @txtSearch
Step: Press Enter
Step: Click on @btnFirstBuy Button
End

  • Data
As Tesbo itself define the combination of both Data Driven and Keyword Driven framework, Tesbo supports data fetch from Excel or even you can pass in the .suite file also. Here we’ll see how you can pass the data in the Tesbo .suite file which can be achieved by keyword ‘DataSet’ with data in JSON format.

DataSet:
{
"Credentials": {
"userName":  "Step2QA",
"password": "pwd@123",
}
}

Test: Login on Amazon DataSet (global data) Credentials.
#Login
DataSet: Credentials
Step: Enter {userName} in @txtUserName
Step: Enter {password} in @txtPassword
Step: Click on @btnLogin Button
End

  • Priority and Severity
One of the coolest advantages of Tesbo is, you can even define Priority and Severity of your test. So when required to run the high priority tests, you don’t go through each and every suite for finding and running it, you just simply pass the priority and severity in your config file and rest will be taken care by Tesbo!

Test: Verify Login With the valid credential
#Login
Priority: High          // can be Low, Medium, High
Severity: Critical      // can be Low, Medium, Major, Critical
Step: Enter 'username' in @txtUserName
Step: Enter 'pwd@123' in @txtPassword
Step: Click on @btnLogin Button
End

Below is the small example of the Tesbo suite file, how it looks like with the Tests.

SuiteName: Tesbo Demo

Test: Search iPhone in Amazon
#iPhone #amazon #T16 #regression
Priority: High
Severity: Medium
Step: Open URL 'https://www.amazon.in/'
Collection: Login to Amazon
Step: Enter 'iPhone X' in @txtSearch
Step: Press Enter
Step: Scroll to Bottom
Step: Scroll to Top
Step: Scroll to @imgiPhone1
Step: Scroll to Top
Step: Scroll to Bottom
Verify: @lblAustralia text is equal ignore case 'Australia'
Step: Pause 1Sec
End

So this is all the default Tesbo command which you’ll need when you start your Tesbo test first.
In the next section, let’s see one of the important parts of the automation. yup right, Configuring our test to start the automation. #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
Accessibility