FUNCTIONAL REQUIREMENTS DOCUMENT

1
Overview and Current Implementation
This Document outlines the Functional Requirements for the Front End UI design implementation
for the existing Selneium automation framework. Currently front end has been designed with
below fields with it’s values coming from an external .json file:

• Environment
• Browser
• Appplication type
• Automation Test Module
• Automation Test Cases
• Login User: i.e from which type of user internal or agent user they need to execute the test case
• Insuredname
• Businessentity
• Insurancetype
• nofoBuildings
• noofLocations
• classcodenumber
• state
• accounttype
• organisationcode

Requested Implementation

1. Implementation of Front End UI design

• We will need to develop Front End UI design implementation for the existing
Selenium automation framework.
2. Need to little bit refactor the existing frond end code based on the further implementation.

Pre Requisites
Below are some of the pre requisites needed for the front end ui design implementation:

• Java 8 version
• Maven swing dependency
• Windows Builder Editor 1.9.5 eclipse plugin for designing front end UI design

2
Front End System Work Flow

3
Requirements
Frond End (Swing GUI implementation):

1. Initially user need to launch the swing gui .jar file on their machines from their extracted automation
framework folder.

2. Next , after launching the .jar file , screen will look like below:

4
3. Front end system will be displaying above fields with values (like application type , test module, test cases)
been populated from an external file like .json. We can have single or multiple .json files based on our needs.

4. Now on the GUI user need to create the test data for the number of automation test cases which they need to
execute from their end.
5. Below are some mandatory fields user need to fill up in order to run the automation suite:
• Environment
• Browser
• Appplication type (Portal , Policy Center)
• Automation Test Module (like
BOP_PolicyCenterTests,BOP_End2EndTests,GL_End2EndTests,Property_PolicyCenterTests, etc)

• Automation Test Cases: like the different test cases they need to execute , they can execute single test
case as well, so based on that user need to create their test data. For eg: if 2 automation test cases are
selected then test data would be created for 2 test case , if 1 then 1 test data will be created
accordingly.
• Login User: i.e from which type of user internal or agent user they need to execute the test case
• Insuredname
• Businessentity
• Insurancetype
• nofoBuildings
• noofLocations
• classcodenumber
• state
• accounttype
• organisationcode

Note: The above field will be subjected to change , and basically front end main focus will be to display
only minimum no of fields (or common parameters) required for the test cases to run.

6. Front end will display necessary validations for the required fields, so that end user does not miss any field
blank required for a test case to run, or which makes our fron end sytem break.

5
 7. Front end system will have a table displayed at the bottom of the GUI , which basically displays how many test
cases test data have been created till now.

8. After user completed filling their test data for their selected test cases , then next step is to save and export the
test data . Here in this step at back end an excel or Test Plan will be created , which will be populated by the
test data which the end user has created from the frond end.

9. Few below points need to be keep in mind while creating the excel (Test Plan) is that we need to create the
excel based on the GUI table which we have seen above at the front end. As this table will give us the high
level view of how our test plan will look like i.e how many columns need to be available , how many sheet
we need to create on our excel, how many test cases we need to popoluate in excel, things like these will
create our test plan. And this GUI table will be our main data source through which we can fetch front end
field values and place it on the excel (Test Plan).

Note: The above point will be part of the detailed discussion in future as this will be required lot of anlaysis movinf
forward.

10. Now after test plan is created next step end user need to do is to click on Run automation Suite button in
order to run their automation test cases. Behind the scenes this will run an executeautomation.bat file for
the test caes available in our automation framework. We also need to hide the button or implement some
kind of validation so that this button will be hidden until and unless user first save and exported the data
from their end i.e they should have created the test plan (excel) , because this test plan is the pre step
required for an automation framework to run smoothly.

6
11. Next afte clicking the Run automation suite button , front end will execute the test cases one by one
without the end user intervention.

12. Final step is then user can simply view the updated report from their extracted automation framework
folder and can review the report accordingly.

7
Risk and Assumptions:
For multiple browsers support , framework need to be refactored for most of the existing implemented test cases , so
this will be planned in phase 2 of the implementation.

Any future framework changes will need to be implemented keeping in mind the front end UI.

Out of Scope Items:

Test cases results update on Rally.

8
Mock-up

Mockup 1: When user initially launch the swing ui jar file.

9
Mockup 2:After user select and fill the necessary required field values and save it for single automated test case:

10
Mockup 3:After user select and fill the necessary required field values and save it for multiple test automated test
cases:

11
Mockup 3:After user save the test data and generate the excel data for the automation framework

12
Mockup 4:Final step after user launch the framework bat file in order to run the test cases fo which test data has
been created

13
14