Working with Tosca TBox Selenium Modules and Related Interview Questions

---

Welcome to this Post – “Working with Tosca TBox Selenium modules and Related Interview Questions” discusses about the Tosca TBox modules, their available modules attributes and their implementation. I will also focus on some frequently asked TBox related interview questions on these modules. The complete post is divided into small sections where I am discussing the concepts first and then focusing on the implementation and later discuss about some frequently asked Tosca TBox interview questions. So, go ahead and enjoy reading…

 

Heads Up! Before we start discussing the usage and implementation of Selenium modules present in Tosca, I would recommend if you do not have in depth knowledge on TBox Architecture then please visit the link shared below so that you get an idea on how the TBox framework works when you use the inbuilt TBox modules in your test cases:

To Know more on Tosca TBox Architecture-Click Here

---

Can Tosca and Selenium work together?

Usually projects prefer working with open source automation tools like Selenium and specifically those which have been developed in java or around java. Selenium as we all know can only work with Web Applications, but we cannot ignore other positive perspectives in terms of support to other browsers, os, CICD tools like jenkins, Docker, Suace Labs, frequent updates by the Selenium Community, etc.

I really doubt that you have noticed the fear which Selenium has given to Tricentis team that led to the development of the Selenium related modules. Obviously, many customers must have approached or discussed there constraint that they have some test coverage already done with selenium and want to move ahead with the development and not to start again.

Which is why, Tricentis came up with selenium modules; to support the new and those customers who have test coverage done in selenium. This is also a way of strategizing and covering the dependencies across the project. Plus, making the customer focus on the Tosca capabilities. And of course, making a worldwide presence.

---

Tosca TBox Selenium modules

The Tosca TBox Selenium is a module provided to support Selenium test scripts execution which is either covered as part of your project already or some components which you think can be automated via Selenium like unit test cases.

Whatever your case might be Tosca TBox selenium provides complete support to run and view your test results. These Modules can be used to start Selenium test cases directly from Tosca Commander.

 

The good to know part here is if you have test cases developed with NUnit or JUnit then these test cases are also supported.

Plus you can also execute the DLL or JAR files which contains Selenium1 (RC) and Selenium2(WebDriver) test cases.

Now let’s view the attributes and usage for Selenium modules.

---

The Tosca TBox Selenium module folder contains the following modules:

1. Start Selenium Server

2. Run Selenium Scripts

Start Selenium Server

---

This Module serves to define connection properties for Selenium 1 and Selenium2.

The TBox Start Selenium server Module attributes are discussed below:

 

 

The Module contains the following attributes:

Module Attributes	Description
Selenium Server Path	Use this to specify the path to the Selenium server jar file.
Selenium	use this to define a port for the Selenium server. The Selenium server is by default opened via the port 4444.

 

 

Let’s see an example. Suppose you have selenium server path which you want to invoke and use it for executing the test cases in that case, you will specify the ‘TestStepValue’ for Selenium Server Path which will define the path to the Selenium server jar file that is:

C:\SeleniumJars\selenium-server-standalone-3.x.x.jar

 

---

Run Selenium Scripts

Now, once you have setup the Selenium jar path, it’s time to specify the test scripts to be invoked. For this we have Run Selenium Scripts module.

This is the modules which responsible to invoke the selenium scripts.

 

 

The Module contains the following attributes:

ModuleAttribute	Description
Path	Please specify the path to the test scripts DLL or JAR file that contains the TestMethods you want to execute.
TestClass	In case you want to focus on complete class run, you can define the class from the DLL or JAR file where the TestMethods are located
TestMethod	In case you want to focus on specific testmethods you want to execute, then specify the name here.
Report Directory	Finally, where exactly you would like to view your results, so here you can specify the directory where the test results should be stored.

 

Suppose you want to run the script containing a class called “Web_LoginCheck” and has various TestMethods like “Validate_Username”,”Validate_Password”,etc.

Now Tosca TBox Run Selenium Script module gives you 3 options:

Option 1

You can run all the classes and TestMethods contained within the script jar or DLL. In this case leave the TestStepValue of the TestClass and TestMethod empty.

In this shown example, we have left out the TestStepValue as empty for both TestClass and TestMethod.

Option 2

Since your jar can have multiple test classes to be executed, you might be interested in running only the priority ones for the sake of complete regression run. In this case we can specify only the class name which needs to be focused and executed.

In the shown below example the ‘TestStepValue’ TestClass defines that Tosca should use the TestClass “Web_LoginCheck”.

 

 

Option 3

Similarly, your TestClass can have multiple TestMethods to be executed; you might be interested in running only the priority ones for the sake of smoke execution. In this case we can specify only the class name which needs to be focused and executed.

In the shown example the TestStepValue TestMethod defines that the TestMethods “Validate_Username” and ”Validate_Password” are used for test execution.

---

Test results

Post execution of course you would like to collate the results at one place. By defining the path of results folder, Tosca puts the results in this folder. Just like you view the test results for any Tosca Test Cases in ExecutionEntry similarly, ExecutionEntry will show you the Selenium test run results.

But there is one difference: there is different file format of the test results for different framework which are used while creating the test cases. These formats are HTML file for JUnit and XML file for NUnit .

 

---

Conclusion:

I would like to share with you some interview questions related to Tosca TBox Selenium modules which are advanced in nature and definitely require your Tosca expertise to solve them. To be honest, some of these questions are not completely part of this discussion, instead I want you to find solution when you are working in the project.

Few questions for you to think over, analyze and try arriving at the solution:

 

1. Can we run the selenium scripts via Tosca?
2. To run Selenium scripts, what all configurations are required?
3. Can you debug Selenium code while running scripts from Tosca?
4. Is selenium test result will be shown in the Execution list post execution?
5. Does Tosca Supports Selenium’s entire version?
6. Does Tosca support the filtering of TestMethods?
7. Can you run only execute the TestMethods which are marked as Priority from Tosca?
8. Can you run the Selenium scripts on different machines via Tosca?

Well, this brings me to the end of the discussion “Working with Tosca TBox Selenium modules and Related Interview Questions” where we have discussed some concepts as well as interview questions.

I really hope you enjoyed reading the post. If you have any doubt on this please feel free to add your comment below.

---

And if you like to read more on TOSCA Interview Questions please follow below links:

Tosca Interview Questions – Part 1

Tosca Interview Questions – Part 2

Tosca Interview Questions – Part 3

Tosca Interview Questions – Part 4

---

If you would like to keep track of further articles on TOSCA. I recommend you to SUBSCRIBE by Email and have new articles sent directly to your inbox.