FIRE (Framework for Intelligent and Rapid Execution)

Overview of FIRE Framework ................................................................................................................ 2

To get started on the FIRE Framework, the initial setup steps are as follows:................................ 2
FIRE Repository File Information ........................................................................................................... 4
1. Page Objects :.............................................................................................................................. 4
2. Custom Keywords: ...................................................................................................................... 5
3. Keywords..................................................................................................................................... 8
Test Case File Information ..................................................................................................................... 9
1) Run Configuration ....................................................................................................................... 9
Cross Browser Execution............................................................................................................... 10
Parallel Execution .......................................................................................................................... 11
2. TC_ScenarioActions................................................................................................................... 12
3. Actions-Steps ............................................................................................................................ 12
How do we use Action-Steps in TC_ScenarioActions .......................................................................... 13
TestDataSet ............................................................................................................................... 13
How do we map Test DataSet in the TC_ScenarioActions ............................................................ 14
DATAPOOL ................................................................................................................................ 15
How do we map the Datapool in TC_ScenarioActions Worksheet ................................................ 16
Storing Variable ......................................................................................................................... 16
Custom Methods with Datapool ................................................................................................. 16
Custom method code ................................................................................................................. 18
Global Variables......................................................................................................................... 18
How do we map Global Variable in Action-Steps ......................................................................... 19
Results....................................................................................................................................... 19
Overview of FIRE Framework

Tavant Technologies’ FIRE framework, which stands for Framework for Intelligent and Rapid
Execution, is a ready-to-use automation platform which can be used in a variety of projects
with requirement of less customization and maintenance. It has been developed using open
source tools like Selenium, TestNG, WebDriver and Java.

The FIRE Framework offers three different levels of script writing based on the users’ skill sets.
1. Users with no knowledge of programming
2. Users with basic knowledge of programming/scripting
3. Expert users who can write or enhance custom utilities

This framework is easy to adopt and maintain. It provides flexibility in test data maintenance,
parallel execution of test cases, remote machine test execution and cross browser execution.
It is a planned & structured framework that helps in reducing the risk of negative ROI of test
automation. It also helps in increasing the ratio of test scenarios which can be automated
and increases the coverage of automation.

To get started on the FIRE Framework, the initial setup steps are as follows:

1. Install JDK1.7
a. Visit Java download page
b. Download JDK
c. Install JDK
d. Set Environment variable JAVA_HOME to path (also set path and class path as
shown below) where JDK is installed
i. Variable name : JAVA_HOME
ii. Variable value: C:\Program Files\Java\jdk1.7
e. Open command window and test java installation by typing java –version

2. Download apache-maven-2.2.1 (bin.zip)and configure (apache-maven-3.0.5-bin.zip)

a. Visit http://maven.apache.org/download.cgi
b. Download Maven 2.2.1
c. Extract contents of zipped archive
d. Set environment variable as shown below
e. I) Home variable
i. Variable name : MAVEN_HOME
ii. Variable value: D:\Maven (I,e the maven installed path)
f. II) Path variable
i. Variable name : Path
ii. Variable value: C:\Program Files\Java\ jdk1.6.0_18\bin;
D:\maven2.2.1\bin;
g. III) Class path variable
i. variable name : classpath
ii. Variable value: C:\Program Files\Java\ jdk1.6.0_18\lib; D:\maven2.2.1\lib
h. Restart the machine and then try the command
 i. Open command window and test maven installation by typing mvn –version

3. Copy project “FireKWDemo” to system from SVN

a. Right click on a folder where you would like to check out code and enter svn path
b. Enter your username and password
c. Check out code

(*path: http://svn.corp.tavant.com/svnproj/FunctionalAutomation/trunk/DemoProjects)

4. Download and Install the “apache tomcat-7.0.40” files and extract. Set the variable path

o Variable name : TOMCAT_HOME

o Variable value: C:\Program Files\apache-tomcat-7.0.40\bin
i. Deploy the war into tomcat server (i.e. Take from SVN and copy the
SampleWebapp.war to Webapps folder).

svn path: http://svn.corp.tavant.com/svnproj/FunctionalAutomation/trunk/DemoProjects

ii. Start the tomcat server from command prompt (from the command
prompt, go to the tomcat bin folder path and type the command as
“catalina run” or by clicking on “startup” file from bin folder)
iii. The server can be stopped by command <Ctrl> + C.
iv. Access the sample demo application website using URL >
http://localhost:8080/SampleWebapp/login
User credentials: admin/admin.

4. Download and Install Eclipse http://www.eclipse.org/downloads/ (may be Eclipse

Classic)

5. Copy project “FireKWDemo” to system from SVN ( svn path:

http://svn.corp.tavant.com/svnproj/FunctionalAutomation/trunk/DemoProjects )

6. Run the Command “mvn clean install” from projectNamefolder where pom.xml file is
located.

7. Now open the Testcases.xls from path “..\FireKWDemo\src\test\resources”.

6. Next, click on Setup and RUN Button from RunConfiguration tab.

7. Select appropriate test cases / browser/groups and click on Submit.

8. For browser like IE and Chrome we need download the native drivers from the website

http://code.google.com/p/chromedriver/

http://code.google.com/p/selenium/downloads/list
The FIRE framework contains two different excel files- Repository.xls and a testcase.xls.
These files are located at \Fire\src\test\resources”.

FIRE Repository File Information

The Repository file will be saved as an .xls file and will contain 4 worksheets as mentioned
below:

1. Page Objects

2. CustKeywords

3. Keywords

4. Common Test Data

1. Page Objects :

Page Object worksheet will contain information of how framework can identify each
element in the pages which is available in the application. Each element should have unique
name to identify the objects. Page object has the following fields;

Page/SectionName TargetElementName TargetElementId TargetIdentificationType

 Page/SectionName will be the Page name/Section name where the element is

available.
 TargetElementName will be the element name and is provided by the user
 TargetElementId will be the element identification information
 TargetIdentificationType will be the element identification type and it could be
id/xpath/name/css etc.

*Sample Page Objects Information

How do we map the Target Element Name in TC_ScenarioActions

How do we map the Target Element Name in Actions-Steps

2. Custom Keywords:

The User has the option to create project specific methods whenever it is required. Those
methods will be placed under Custom Keywords section .This allows the user to avail these
methods at a later point.

Custom Keywords Screen has the following fields

 ClassName : Class Name is where the user has written the custom methods.
 MethodName :The user enters his custom methods under this field.
 Description : This field holds the Description about the method
  AliasKWName : This is the Alias name we give for the custom method. Users will use
this name while referring to the custom methods.
*Sample Custom Keywords

ClassName MethodName Description AliasKWName

com.test.DBConnection c:dbConnection Data Base Connectivity Cus_dbConnection

In the above sample the user has created a DBConnection Java Class under the path
src\test\java\com\test\ and created a function/method called dbConnection. The alias
keyword name used in this case is cus_dbConnection .

How do we write custom methods in Eclipse?

The user has to import the project into the eclipse, doing the following steps,
EclipseFileImport Existing Maven ProjectSelect the Project Folder .The user also
has to extend the WebPage to the Java class while writing the Custom methods.

Below screenshot depicts how the user can create custom methods for a specific project.

How do we map the custom keywords in TC_ScenarionActions?

User will provide the custom method name in the Action Field.

Please find the screenshot below

How do we use the custom keywords with multiple parameters in TC_ScenarioActions

The user will pass multiple parameters as a single parameter with a splitter in the I/O Value
field. In the below mentioned example, the user splits the parameter with “:” .User will
separate the parameter in the code. The user will also provide the custom method name in
the Action field and the parameters in the I/O Value field. Please find screenshot below

How to write the custom methods with multiple parameters

How do we define the custom keywords with multiple parameters in the Custom Keywords
Sheet

3. Keywords

All the keywords which are defined in the framework will be displayed in the keywords page
in the repository file. User can use the keywords screen for reference. User will be using an
alias name to use the keywords.

Please refer the keywords available in the framework:

Test Case File Information
The Testcase.xls file has the following worksheets;

1. Run Configuration

2. TC_ScenarioActions

3. Action-Steps

4. TestDataSet

5. DataPool

1) Run Configuration

The Run Configuration sheet incorporates the button called ‘Setup & Run’. Clicking on the
button allows the user to initiate the test run.

Clicking on the Setup & Run button causes the following Screen to popup.
URL – Application URL could be provided here.

Browsers- User has the option to run the tests in cross browser execution and currently fire
framework supports 3 different browsers –Firefox, Internet Explorer and Chrome.

Run Tests Parallel –This feature allows the user to run tests in parallel.

Select TestCase Sheets – User can select which testcases to run.

Select Groups To Run – All the groups which are mentioned in the TC_ScenarioActions sheet
will be displayed and user can select the group which is required while running the tests.

Cross Browser Execution

Cross Browser Execution option allows user to run the test cases in multiple browser which
selected by the user.

Let’s Say user selects the option Cross Browser Execution and selected the browsers FF and
IE. So the test cases we selected will be executed in FF and IE browsers one after other.

We can see a Sample in cross browser execution below.

The above Selection will execute all the Test cases which fall under the Group name
“smoke” in Firefox and IE one after other. It means that Test Cases will run Firefox andthen
later in IE.

Parallel Execution
Parallel Execution option allows the user to run tests in parallel by opening multiple instances of the
browser and running the tests simultaneously.
 2. TC_ScenarioActions

Test Scenario ID Scenario Description Group/Type Action TargetElement I/O Value

TS-101 Verify for Valid User Login Smoke Login As Admin
TS-101 Test Scenario Scenario Fire_verifyText UserNameLable Hi, admin
ID Description Group/Type Action TargetElement I/O Value
TC_ScenarioActions sheet has the following fields available

 TestScenarioID –Unique ID will be provided for each test cases

 Scenario Description – Test Scenario/ short description will be provided.
 Group/Type – User will provided the Group/Type of the Scenarios (Eg:
Smoke/Regression/Functional)
 Action Description –Action Description will be provided
 Action –Action details should be provided .This Action details will be mapped to the
Action-Steps worksheet.
 TargetElement – Provide the Target Element name if any
 I/O Value -Provide the I/O Value, if any

User can have multiple scenario sheets starting with the name ‘TC_’ followed by the test
case file name.

Testcase file name format should be TC_<TestCase File Name>.

Please find the sample TC_ScenarioActions Sheets

*Sample TC_ScenarioActions sheets

3. Actions-Steps

Actions-Steps sheet will have the following fields

Action Step Description Command TargetElement Value

Actions are nothing but the Methods/Functions. In order to avoid redundancy, the user can
use the action statement to cover a series of steps.
Let’s say a user wants to write an action called ‘Login As Admin’ .User will accept the inputs
called “Username”, “Password” and then Clicks on Login/Submit Button .These details can
be written under an action as mentioned below.

Action Step Description Command TargetElement Value

Login As
Input UserId Fire_type UserID admin
Admin
Login As
Input Password Fire_type Password admin
Admin
Login As Click Login
Fire_click LoginButton
Admin Button
Login As
Fire_waitUntilDefaultTimeout
Admin

Here Action will be the method/Function Name and Step Description will provide the each
step description .Command will be the Keywords which are defined in the framework.
Commands will be mapped from the Keywords sheet in the Repository. Target Element will
be the object names and this will be mapped from the PageObject in the Repository file and
the value will be the user input values.

How do we use Action-Steps in TC_ScenarioActions

Actions which are defined in the Action-Steps sheet will be used in the Action field in the
TC_ScenarioActions sheet. We can also use the keywords directly in the Action field in
TC_ScenarioActions. Please refer the below screenshot.

TestDataSet
TestDataSet will be used if the user needs to use specific data set for the test
cases.TestDataSet Sheet will have the following fields

TDSet ID Variable Value

TDSetID: Data Set ID will be provided and TDSetID will be given in the I/O Value field in
TC_ScenarioActions Screen and the corresponding value which is given in the TestDataSet
will be used towards the variable/TargetElementName.

Variable: Element Name where user wants to pass the value will be provided and Target
Element Name should be mapped to Target Element Name in Repository File.

Value: Input Value will be provided.

Please find the Sample TestDataSet below

TDSet ID Variable Value

TD_SSN SSN1 898
TD_SSN SSN2 89
TD_SSN SSN3 8989

How do we map Test DataSet in the TC_ScenarioActions

Please sample TC_ScenarioActions sheet with Test Dataset Below

Above Example, Test DataSet ID will be provided in the I/O Value field in the
TC_ScenarioActions sheet.

How do we use Test DataSet in the Action-Steps

User will provide the Test Dataset ID in the value field in the Action-Steps Sheet. Please refer
the below screenshot

DATAPOOL
DataPool basically used for Data Driven Tests. User can have multiple Datapool and
datapool name defined by the user. Datapool sheet will have the following fields.

TestCaseID TestDataId Variable1 Variable2 Variable3 Result

TestCaseID is nothing but the TestScenarioID

TestDataId is unique identification number.

Variable1, Variable2 and Variable3 are the different variable names

Variable field holds value which is referred to by the target element field in repository file

Result: This is the Result variable Name.

Please Find the Sample Datapool below

TestCaseID TestDataId SSN1 SSN2 SSN3 SSN

TS-107 1 555 55 5555 555-55-5555
TS-107 2 666 66 6666 666-66-6666
TS-107 3 777 77 7777 777-77-7777
*Datapool name is SSNDATAPOOL
Whenever user wants to use the SSNdatapool, the SSNdatapool name will be given as the
I/O Value field in the TC_ScenarioActions sheet. It will be in the form of dp:SSNdatapool
where the SSNdatapool is the name of datapool.

How do we map the Datapool in TC_ScenarioActions Worksheet

Above example, user has used data pool called SSNDATAPOOL in the I/O Value in the
TC_ScenarioActions.

Syntax to use the datapool in the TC_ScenarioActions worksheet is dp:<DataPoolName>

Storing Variable
User can store value to a variable and use it whenever it is required in the test cases. So We
have introduced this feature in FIRE using the keyword “Fire_storeValue” .User can store
value to a variable and variable name can be defined with ‘var_<variable name>’ .

Please find the sample of storing a value to a variable and use that variable in the test case.

Custom Methods with Datapool

User can use custom methods with datapool. Please refer the below screenshots.
Custom method code

Global Variables
User can define global variable and use it wherever it is needed. So a global variable will be defined
under CommonTestData sheet in Repository file.

Please find the Global Variable defined below

Variable Value
user Admin
pwd Admin
*Global Variable defined in CommonTestData Sheet

How do we map Global Variable in TC_ScenarioActions

Above example, user using the global variable with in “{}” in I/O Value field and the
corresponding value which is defined in the CommonTestData sheet will be passing to the
TargetElement.

How do we map Global Variable in Action-Steps

In the above example, the user is using the global variable with in “{}” in the Value field and the
corresponding value which is defined in the CommonTestData sheet will be passed to the
TargetElement.

Results
Result folder and reports will be created/generated once the test execution is completed. User can
navigate to the test execution reports by clicking on the Open Report button in the Test Run
Configuration window. Refer the screenshot below:

When a user clicks on the “ OpenReport” Button ,the Test Execution Report page will be opened and
this report will provide detailed information about the test execution like: Total Test cases, Total
Testcase passed, Total Testcase Failed and Total Testcase skipped with Detailed Result Report .
Please find the Test Execution Report screenshot below:

Another way to access the Result file is by navigating to the test-output folder with Date and
Time stamp and clicking on Result.html file. The test-output folder with date and time stamp
will be created under project folder. Please find the Test Execution Report screenshot
below.
When any test case fails, the Test execution report page will provide a hyperlink which provides the
reason to why the Testcase failed. Please find the screenshot below:

In the case of a Testcase failure, a screenshot of the failed scenario will be created and it will be
located under the test-output folder and the path for it is

“Test-output folder” with date and time stamp > screenshot > Browser > folder.The filename for the
screen shot would be <test case name>.png.
Please Refer the below screenshot :