Documentation





1. Introduction

Think Future Automation Generic System also known as TAGS is a generic framework which has been specifically designed to cater to needs of any client who seeks a low cost end-to-end test automation solution for web using open source tools.TAGS is designed in such a manner that the testers do not need to possess any scripting background at all to automate complex testing scenarios. Everything is already built-in and can be configured easily.


Primary characteristics of TAGS:

  • Should support multiple web browsers: Internet Explorer, Firefox, Safari, Chrome etc.
  • Should incorporate the 4Rs: Repeat-ability, reliability, re-use and robustness.
  • Should be a user-friendly solution

TAGS is composed of the following components:

  • Test Engine: is the brain of the framework which will handle all other components
  • Test Driver: will drive automation tools like Selenium integrated with TAGS framework
  • Reporting Engine:will generate reports/log files for automation execution and email notifications.
  • Test Manager:will be responsible to retrieve data from different test management source systems (E.g. File System).



2. TAGS Philosophy

As with Selenium and other automation tools testers need to know at least one of the supported language very well in order to automate your application successfully but with TAGS Framework testers don’t need knowledge of any programming language. TAGS Framework is designed in such a manner that the testers do not need to possess any scripting background at all to automate complex testing scenarios.Also Selenium does not have inbuilt reporting capability so testers need plugins like JUnit and TestNG for test reports. TAGS overcome this limitation of selenium with its Reporting Engine. It automatically generate reports/log files after execution of tests and also send Email Notifications.Selenium does not handle various browser pop-ups but TAGS provide various Recovery Scenarios to handle these pop-ups.




3. SUPPORTED PLATFORMS

  • Supported Operating Systems
    • Windows ( XP, Vista, Win 7 , Win 8 and 8.1)
  • Supported Browsers
    • Google Chrome 29 or later

    User need to download chromedriver.exe and placed at bin folder, user can see the list of driver with respective supported versions of chrome from Here default driver version is v2.10 placed at bin folder

    • Mozilla Firefox 19.0 or later (upto 31.0)
    • Internet Explorer 7.0 or later

    Version IE 11 only requires additional configuration, you will need to set a registry entry on the target computer so that the driver can maintain a connection to the instance of Internet Explorer it creates.

    For 32-bit

    Windows installations, the key you must examine in the registry editor is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\Feature Control\FEATURE_BFCACHE

    For 64-bit

    Windows installations, the key you must examine in the registry editor is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\Main\Feature Control\FEATURE_BFCACHE Please note that the FEATURE_BFCACHE sub-key may or may not be present, and should be created if it is not present. Important: Inside this key. Create a DWORD value named iexplore.exe with the value of 0




4. Pre-Conditions

  • Must have .Net Framework 4.0 or above
  • If your system does not have Microsoft office installed then install Microsoft office .
  • In Case Microsoft office is not available due to license concern then you can install Kingsoft Office (free) from Here or Apache Open Office (free) from Here and install Microsoft Access Database Engine from Here.
  • For writing Test cases you need any of above office tool.
  • For IE browser if only issues occur during execution then it is recommend to setup all security settings at same level.

How to do :

  • Open Internet properties by run command “inetcpl.cpl”
  • Click on security tab
  • Click on zone “internet”
  • See the level and checkbox status and set same level and checkbox to all zones according to internet zone. (ie : “local intranet” , “trusted sites” and “restricted sites”)
Image

Note: If you installed 32 bit MS office on 64 bit Operating System then you must install 32 bit version of TAGS on that 64 bit OS.




5. Installation

  • Download the setup file (32 or 64 bit) from www.tagsframework.com
  • Now Run the setup and follow the instructions.

  • Click on Next button
  • Image
  • Accept End user licence agreement
  • Image
  • Browse the Installation folder path and click on Next button
  • Image
  • Click on Install button
  • Image
  • Installation in progress...
  • Image
  • Click on Finish button
  • Image
  • Verify Installer in Add/Remove program list
  • Image



6. Testing Process

Testing with TAGS involves 4 main stages:

Creating Tests

  • Now write your test cases in a Excel sheet.
  • Prepare Object repository in a Excel sheet (ObjectRepository.xlsx).

Configuring Test:

After writing your test cases and preparing object repository you need to configure your test cases. For configuration follow the steps given:

  • Go to the installation folder of tags and search for the “parameters.ini” file.
  • Open the file and change following parameters according to your Test:
    • LogDestinationFolder
    • TestCaseId
    • TestSuite

Running Test:

After configuring you can run your test by just running TAGS.exe file or double clicking tags shortcut on your desktop.

You can also set parameters by sending them through command line. E.g. C:>TAGS.exe testcaseid=abc.tc01

Analyzing Test Results:

After test execution completed reports are generated in the Results folder. Reports are generated in two forms

  • Zip form: All HTML reports are zipped in a file. User can use these reports by unzipping the zipped file.
  • Unzip form: All HTML reports are placed in Results folder by the TAGS Reporting Engine



7. Quick Start

  • Download and install .net framework (above 4.0) if not installed .
  • Download and install any office tool if not installed already in your system.
  • Download the installer from Here according to your system configuration(32/64 bit).
  • Run and Install the installer.
  • After Install goto location C:\Program Files\TFTPL.
  • Goto TAGS folder.
  • Here you will find six sub folders.
  • Image
  • Majorly you need to work with only three folders.
    • ObjectRepository
    • Results
    • TestCases
  • ObjectRepository : You will find one sample spreadsheet named ObjectRepository.xlsx
  • Image
  • This is sample spreadsheet where you can add object,there is a particular format describe below
  • Image
    Note : To identify objects please refer Element Locators Strategies in TAGS sheet
  • Results :After execution result placed at this location. User can analyze the results by opening any one of the files
    • Html file
    • Zip file
  • TestCases :
    AHere you will find two files one SampleTest.xlsx and one Common.xlsx
  • Image
  • These are sample spreadsheets where you can write your test cases,there is a particular format describe below
  • Image
  • After preparing Test Cases and Object Repository, Now need to specify few parameters in parameters.ini file placed at bin folder
    • Major parameters:
    • Browser (by default : firefox)
    • TestCaseId (by default : SampleTest Case Ids)
    • Environment (by default : Production)
    • TestCaseTimeOutInMinutes (by default : 30 min)
    • EmailNotification (by default : false)
  • After finishing these jobs just Launch TAGS.exe shortcut placed at desktop or application placed at bin folder.
  • After execution user can see the results uploaded at Results folder.



8. Send Notification Mail

TAGS Reporting Engine automatically sends Email notifications

  • At the Start of test Execution.
  • At the End of test Execution.

For Email notification user must change following parameters in “parameter.ini” file:

EmailNotification: true

Value of this parameter must be true.

EmailNotificationFrom: Specify the source email address.

EmailSMTPServer: Specify SMTP mail server (E.g. Smtp.gmail.com).

EmailSMTPPort:Specify SMTP Port number.

EmailSMTPUsername:Specify username for login.

EmailSMTPPassword: Specify password for login.

EmailStartTemplate: templates/StartTemplate.txt(inside templates folder) Specify the location of start template file. This template is used to create email at the start of test. User can change “StartTemplate.txt” file according to its needs. StartTemplate.txt file includes the following attributes:

[Test Cases]: Name of the test cases (For instance, ABCPhase2.01)

[Test Suite]: Name of the test suite (For instance, ABCPhase2)

[Name]: Name of the recipient.

[RemoteUrl]: URL of the remote machine on which the test case execution has started.

[StartTime]: Starting Time of execution.

EmailEndTemplate: templates/EndTemplate.txt(inside templates folder) Specify the location of end template file. This template is used to create email at the end of test. User can change “EndTemplate.txt” file according to its needs. EndTemplate.txt file includes the following additional attributes:

[Result]: Status of the Execution Report (It is either ‘Pass’ or ‘Fail’)

[Environment]: Testing environment (Environments can be QA1, QA2, or QA3)

[EndTime]: Ending time of execution.

[ExecutionTime]: Total time for execution.

Note: Variable enclosed in square brackets ( E.g.[Test Cases] ) in “StartTemplate.txt” and “EndTemplate.txt” are replaced by TAGS reporting engine at run-time.

For Sending mail user must give recipient names in EmailNotification.ini file. Description of EmailNotification.ini is given below:

EmailNotification.ini file:

This file includes the name and email id of the recipient.

Details of parameters within EmailNotification.ini file

The EmailNotification.ini file includes name of the recipient and the email id at which the notification is to be sent. The format is as follows: Recipient Name|Email ID




9. Recovery Scenarios

The recovery scenarios folder includes different scenarios that would come into play at the time of an unexpected exception or pop-up. That means, whenever a test step executes (like refreshing or navigating to another page), it verifies from the recovery files whether that particular object (any pop-up, modal, etc) has been identified on the screen or not (mentioned objects in the recovery files), if it finds, then it will automatically perform the defined actions against it.

Recovery is basically of two types:

  • Recovery from browser.
  • Image
  • At the End of test Execution.
  • Image



10. Execution Environment

  • Production
  • QA
  • Any

There are only two .ini (Production.ini and QA.ini) files in which you can initialize parameters (ie : application url, object timeout etc)

You can even categories combinations of Test Cases (ie : Lets say few Test Cases user want to run under different condition (ie : QA) and few under another different condition (ie : Production)

There are only two .ini (Production.ini and QA.ini) files in which you can initialize parameters (ie : application url, object timeout etc)

How to use this feature :

  • Search for parameters Environment and Keyword in parameter.ini file
  • User can add keyword values separated by comma in keyword section.(ie : Keyword: Production,QA,Any)
  • Out of above added keyword user can add environment value only one value can be assigned to Environment. (ie : Environment:QA).
  • In Test Cases user need to specify test case category under keyword column (ie: Any,QA or Production) like this.
  • Image
  • For example if user will assign QA value of Environment in parameters.ini file then only those Test Cases will run which are categories as QA in Test Cases
  • If there is no concern of environment then only assign Any to Environment,in that case all test cases will doesn’t matter those are categories as QA,Production or Any.
  • User either can add /update parameters in these files or can left blank these files. But file must be there. (by default blank files).



11. Test Case Sheet

Test Case sheet is a spreadsheet used to write test cases. This sheet must be in specific format to successfully run the test cases. Format of spreadsheet is described below:

keyword test_scenario test_case_id comments parent test_object step_action data Iteration options
  • Keyword: This field specify the execution environment of the test case.
  • Test_scenario: This field contains the description of test-case.
  • Test_case_id: It refers to the id of test case. Test case id must be unique. Format to define test case id is test_suit_name.test_name (E.g. SampleTest.test_case_01). Test suit name is same as the test-case file name.
  • Comments: This field contains user comments related to the test-case. These comments are used in reports. If this field is blank then reporting engine automatically generate comments in report by combining step_action, data, parent and test_object fields.
  • Parent: It refers to the page on which web object is present.
  • Test_object: It refers to the test object present on web page. The combination of Parent and Test_object fields used to uniquely identify test objects on the web pages.
  • Step_action: It refers to the action to be performed on the test object.
  • Data: This field contains data related to the action
  • Iteration: It refers to the row number of the test-data sheet
  • Options: This field includes certain keywords such as: Optional {optional}, Ignore Case{ignorecase}, Partial Match {partmatch}, Ignore Space {ignorespace}, Skip/Ignore {skip}{ignore}



12. Test Data Sheet

The test_data sheet should include the required input data for test case execution. It includes the column name, row # and the data which needs to be entered while execution.

Iteration: To execute a test case multiple times with different data, it would be handled by Iterations method. It can be distinguished with unique row numbers. Like as shown below: if we’d like to enter Username as ‘matchtft’ & Password as ‘test’ then while execution in the iteration column of the test case sheet we would mention 1-1.

For eg: See the sample attached below (Fig: ) for your reference

Image

The Test Data sheet may include more than one sheet depending on test case requirements.




13. Object Repository Sheet

Object Repository spreadsheet is used to store all web objects which are used in your test cases. The format and brief description of spreadsheet is given below:

sl_no parent test_object logical_name locale obj_type how what comments mapping
  • sl_no: Serial number.
  • parent: It refers to the page on which web object is present.
  • test_object: t refers to the test object present on web page. The combination of Parent and Test_object fields used to uniquely identify test objects on the web pages.
  • logical_name: It contains the description of test object which helps testers to identify objects.
  • locale: language option in which the website under test is to be displayed.
  • obj_type It contains information about type of web object. E.g list, textbox, button, link etc.
  • how: This tells the TAGS engine how to locate web object. E.g. id, xpath, tagname etc
  • what: This contains the value of locator.
  • comments: This includes any comments regarding the objects on a web page.
  • mapping: This refers to mapping the logical name of the object with the internal attribute.



14. Reusable Test Cases

Basic purpose of this feature is to create single test case and use it where ever required

This can be achieved by two ways

  • Write Test Case within same Test Case sheet
  • Create New Test Case file (ie : Common.xls)

Write Test Case within same Test Case sheet :

Create test case and use this with in the sheet by using TAGS keyword : runexceltestcase followed by Test Case Id.

Image

Example :For booking of flight,status of flights,cancellation of flight and for more operations user need to login so we can write one single test case for login and use this test case where ever required.

Create New Test Case file (ie : Common.xls)

This is some how similar to Test Case sheet, this sheet must be in specific format to successfully run the test cases. Format of spreadsheet is same as of Test Case sheet

How to use this feature :

  • Specify parameter GlobalActionFile value in parameter.ini file.(ie : GlobalActionFile: Common.xls)
  • Create Test case file (spreadsheet) in specific format given above.
  • Specify sheet name (like : Login) and write test case according sheetname
  • Test case Id must be according to sheetname (ie: )  Ex : Login.01
  • At last specify test case to be called via another sheet under step action column
Image



15. TAGS Keywords

S.NO KEYWORD DESCRIPTION PARENT TEST OBJECT DATA
BROWSER OPERATIONS
1. openbrowser Opens the browser. If used without the 'Test Data', it opens a blank browser. If used with 'Test Data', it opens the browser and navigates to the URL mentioned in 'Data Column'. Test Data :- URL (optional)
2. clearbrowsercache Clears the Browser cache
3. closebrowser Closes the running Browser.
4. closeallbrowsers Closes all the running Browsers.
5. refreshbrowser Used to Refresh the Browser.
Navigational Keywords
1. navigateurl Used to Navigate to a specific URL given in 'Data Column'. URL as Data
2. goforward Used to Go to the next Page.
3. goback Used to Go Back to the previous Page.
Web Form Operations
1. clear Used to Clear the text present in a text Box. Need Parent Need Test Object
2. enterdata Used to enter Text in the Text Box. The text to be entered is given in the 'Data Column Need Parent Need Test Object Test Data
3. enteruniquedata Generates and enters Unique Data in the given Object. The length of the Unique Data to be generated is given in 'Data Column' Need Parent Need Test Object Length of Data to be generate
4. click Used to Click on a specific Object. Need Parent Need Test Object
5. check Used to Check the CheckBox. Need Parent Need Test Object
6. uncheck Used to Uncheck the CheckBox. Need Parent Need Test Object
7. selectitem Used to select a specific option from a List. The Object is the locator of the list. The Option to be selected is given in 'Data Column'. Need Parent Need Test Object Text of the item to be select in dropdown
8. selectmultipleitems Used to select multiple item in multiple selection box Need Parent Need Test Object Text of the items to be select seperated by comma
9. selectitembyindex Used to select a specific option from a List. The Object is the locator of the list. The Index of the Option to be selected is given in 'Data Column'. Need Parent Need Test Object index number of Item to be select
Wait Keywords
1. wait Used to pause the execution for a static time. The amount of time is mentioned in 'Data Column'. Time should be in second in test data
2. waitforobject Waits for particular Object to Appear. Need Parent Need Test Object Time out in second(optional)
3. waitforobjectnotpresent Waits for a particular Object to Disappear. Need Parent Need Test Object Time out in second(optional)
4. waitforproperty It waits for Property to appear. The property to wait for and the timeout is given in the 'Data Column'. Unit of timeout is seconds. Syntax -- property | timeout Need Parent Need Test Object property | timeout in second
Alert Handling
1. acceptalert Accepts the Alerts.(browser Alert)
2. dismissalert Cancels the Alerts.(browser Alert)
3. verifyalerttext Verify text of the alert. The text to be verified is given under the 'Data Column'. Text to be verify
Verify Keywords
1. verifytextcontained Verifies the text contained as a substring of a Word in the given Object. The text to be verified is given in the 'Data Column'. If it does not find the object in the 'Object Repository', it verifies the text (given in data column) to be present on the entire page. Need Parent Need Test Object Text to be verify
2. verifytextnotcontained Verifies the Text is not a substring of a Word in the given object. The text is given in the 'Data Column'. Need Parent Need Test Object Text that verify as not present
3. verifytextonpage Verifies that the specified text is present on current web page. The text to be verified is given in the 'Data Column'. Text to be verify
4. verifytextnotonpage Verify that specified text is not present on current web page. The text is given in the 'Data Column'. Text that verify as not present
5. verifylistitempresent Verify that List option is present in specified List object Need Parent Need Test Object Text of item present in dropdown
6. verifylistitemnotpresent Verify that List option is not present in specified List object Need Parent Need Test Object Text of item not present in dropdown
7. verifyobjectpresent Verifies that the specified test object is present on current web page. Need Parent Need Test Object
8. verifyobjectnotpresent Verifies that the object is not present on current web page. Need Parent Need Test Object
9. verifyobjectproperty Verifies a specific property of the given Object and matches it with specified value. Syntax - PropertyName | ValueOfProperty (To be given in 'Data Column'). Need Parent Need Test Object PropertyName | ValueOfProperty
10. verifyobjectpropertynot Verify the given property is not for Object Need Parent Need Test Object PropertyName | Value Of Property that is not present
11. verifypageproperty Verify page url \ title url or title
12. verifytextinpagesource Reads the html of the page, and searches for the specified 'text'. The text is given in 'Data Column'. Text to be verify in page source
13. verifytextnotinpagesource verify the Given Text is not present in page source. The text is given in 'Data Column'. Text that verify as not present in page source
14. verifypagedisplayed Verifies that the URL of page is as per the page object given in OR Need Parent Need Test Object
15. verifyobjectdisplayed Verifies if the object is being displayed or not on current web page
Database Operations
1. executedatabasequery Execute a data base query. The query is given in 'Data Coloum'. Need sql Query
2. getdatafromdatabase Get all the record from database using specified query Need sql Query
3. getuserfortesting Get all the record from database using specified query but if no record found then test will terminate instantly Need sql Query
XML Operations
1. findxmlattribute To find a attribute in XML attribute name
2. verifyxmlattribute verify the Xml attribute is present attribute name
3. countxmlnodes Used to Find the Count of Given Xml Node XML node
4. verifyxmlnodecount Used to verify the Count of Given Xml Node XML node | count
Events and Actions
1. mousemove To focus on Specific Object. To move the cursor to a specified Object. Need Parent Need Test Object
2. mouseclick To click on a Specific Object. Need Parent Need Test Object
3. mouseover To Hover the cursor on a Specific Object. Need Parent Need Test Object
4. keypress Used to press a Specific Key on a particular Object. The key to be pressed is given in 'Data Column'. Need Parent Need Test Object Key name: e.g . ENTER
5. fireevent Used to focus on an Object and perform an event mentioned in the 'Test Data' Need Parent Need Test Object Test Data:- (Event name e.g. blur)
6. addaction It saves an Action in an Array in the form of list. The action is given in the 'Data Column'. Need Parent Need Test Object e.g. click
7. performaction It executes the list of actions saved in the add action list.
Miscellaneous
1. runexceltestcase Runs a particular test case. The test case ID to be run is given in the 'Data Column' Test Data- (Test Case ID of the TestCase to run)
2. settestmode Similar to If Else statements. It is used for AB Testing. It first checks which page is coming up and then performs an action corresponding to that page. Need Parent Need Test Object <Mode Name> | value
3. getpageproperty Stores the page Url/Title in a given variable. The variable is given in the 'Data Column'. ( Variable to store and the url/Title (e.g url | <Variable> )
4. executestatement Execute a java script Java Script
5. setvariable It sets a value to a variable <Varibale name> | value
6. setparameter Used to override the Tags parameter at run time, it needs to put at first step of the test case in data column <Tags parameter> | value
7. requestwebservice Execute a API Query with specified Method Api query
8. downloadfile It downloads the file to a particular location in the System and save the location in a variable 'downloadedfile'.
9. ftpfileupload It uploads a file to ftp server Ftp server url | username | password | file path to be upload
10. generaterandomnumber It generates a Random number . The limit of the random number is given in the 'Data Column'. <lower limit> -<Upper limit>
11. generateuniquestring It generates the unique String. The length of the string to be generated is given in the 'Data Column'. Length of string to be generated
12. getobjectproperty It extracts the value of the property of a particular object and puts it in a variable. Need Parent Need Test Object <property name> | <variable name>



16. TAGS Parameters

  • Browser: Specify browser name (E.g. Firefox, chrome, ie)
  • Driver: Specify driver name (E.g. Selenium)
  • TestCaseLocation: Specify the path of test-case excel sheet
  • TestDataLocation: Specify the path of test-data excel sheet
  • TestCaseId: Specify the Test case ID
  • TestSuite: Specify the Test suite name. It must be same as name of test-case excel file
  • TestCaseFileExtension: Specify the file format of test-case file (E.g. .xlsx, .xls)
  • GlobalActionFile: Specify the common (reusable) file. This file should be in the same location where the test data is stored
  • ORLocation: Specify the path of Object Repository Excel sheet
  • ORFileName: Specify the name of Object Repository Excel sheet
  • RecoverFromPopupLocation: Specify location of pop-up Recovery Scenarios
  • RecoverFromBrowserLocation: Specify location of browser Recovery Scenarios
  • RecoverFromPopupFileName: Specify name of file which recover from pop-ups
  • RecoverFromBrowserFileName: Specify name of file which recover from browser
  • LogFileName:Specify Name of the file where the logs are created
  • LogDestinationFolder: Specify the path where log/reports are to be generated
  • ManagerType: Specify the test management source systems (E.g. File System, XStudio)
  • TimeFormat: Specify the time format
  • DateFormat: Specify the date format
  • DateTimeFormat: Specify the date-time format
  • CompanyLogo: Full path with filename of the image to be used as the logo
  • FailedCountForExit:Refers to the maximum number of consecutive steps that can fail before the. Execution is terminated. Use 0 for no limit
  • EndExecutionWaitRequired: Specify whether to wait or not for user response after execution of the test
  • DBTestDataLocation: Specify the location of Database Test data
  • DBConnectionString: This contain the Database connection string if test need Database Access
  • DefaultDb: Mode to work with db (default is write mode)
  • DBServer: Default database server name/ip
  • DBTestData:
  • DBQueryFilePath: Specify the path of file in which database queries are stored
  • UploadResultsToDB: Specify whether to upload Results on Database or not
  • ResultsDBConnectionString: Specify connection string for result upload on DB
  • DebugMode: This parameter highlights the each and every step at run time
  • ErrorCaptureAs: This determines whether the page at which error has occurred should be captured in the form of an image or HTML file
  • Environment: Specify the environment of test execution
  • Keyword: Used for Filtration of environment
  • EnvironmentSetupBatch: Name of the batch file required for fulfilling certain pre-conditions before the execution of the test cases
  • TestCaseIDSeperator: Specify the test case id separator
  • TestCaseIDParameter: To determine testcase file name
  • SnapshotOption: Specify when to take snapshot
  • RunRemoteExecution: This parameter determines whether the automation tool should run on a remote machine or no
  • RCMachineId: Specify Remote machine id
  • RunOnRemoteBrowserUrl: Specifies the URL of the remote machine at which the execution should be carried out
  • EmailNotification: Specify whether to send email notification or not
  • EmailNotificationFrom: Includes the email id of the sender
  • EmailSMTPServer: Specify SMTP mail server (E.g. Smtp.gmail.com)
  • EmailSMTPPort: Specify SMTP Port number
  • EmailSMTPUsername: Specify SMTP username for authentication
  • EmailSMTPPassword: Specify SMTP password for authentication.
  • EmailStartTemplate: Specify the location of start template file. This template is used to create email at the start of test
  • EmailEndTemplate: Specify the location of end template file. This template is used to create email at the end of test
  • KeepReportHistory: If value is false then TAGS reporting engine will clean the results folder before generating reports
  • ValidateSetup: It can be true or false. If true then when tags.exe runs, it will check all the prerequisites and validation procedures, if it is false, then it will not check for any prerequisites and validation procedures
  • TestMode: The environment name. Default environment is ‘Control’. This is for A/B mode
  • CloseBrowserOnCompletion: If value set to true it will close the browser after execution of the test
  • FirefoxProfilePath: Specify the location of Firefox profile. Firefox saves user preferred information such as caches, passwords, certificate etc in a set of files called profile, which is stored in a separate location from the Firefox program files. User can have multiple Firefox profiles, each containing a separate set of information. User can use these saved profiles while executing the test cases, in order to execute the re-usable existing profiles. Apart from this, users have an option whether to use the existing profiles or would like to create a profile
  • AddonsPath: Path where Firefox addons are saved
  • ChromeUserAgent: Specify the path of Chrome User Agent
  • ApplicationURL:Specify the URL of web application you want to test. If URL is not given in data section of test-flow sheet then TAGS Engine use this parameter
  • ObjectTimeout: Specify waiting time in seconds for an object to appear on web page. If object not present after wait time completed it raise exception that object not found
  • GlobalTimeout: Specifies the waiting time for all the actions to be performed before timeout
  • MaxTimeoutForPageLoad: Maximum time required for a web page to load
  • MinTimeoutForPageLoad : Minimum time required for a web page to load
  • ScriptLanguage: After execution is completed TAGS Engine generate an external language specific selenium script file of whole test. This parameter specify that language. Currently, TAGS Framework supports PHP and Java as the scripting languages
  • RecoveryCount: Specify the number of times recovery can be done
  • ScreenshotCompressionRatio: Specify the compression ratio of snapshots. The value of this parameter must be in between 0 and 1
  • ListOfUniqueCharacters: "a", "b", "c", "d", "e", "f", "g", "h", "i", "j", "k", "l", "m", "n", "o", "p", "q","r", "s", "t", "u", "v", "w", "x", "y", "z"
  • TestCaseTimeOutInMinutes: Specify the time limit for test to execute completely. If this limit exceeded the test will be terminated automatically.
  • Language: Specify the language (default is “en”).
  • iniFiles: Specify the .ini file.



17. Report Settings

The ReportSettings.ini file includes the text display settings for the execution report generated in HTML format.

Details of parameters within ReportSettings.ini file:

  • ReportFont: Refers to the Font used in the HTML report.
  • ReportFontStyle: Refers to the Font Style used in the HTML report.
  • ReportFontWeight: This parameter is used to specify the weight of the font. For Instance, Normal, H1, H2, Bold are some of the font weight attributes.
  • ReportResultFont: Refers to the font used specifically in the Execution Report within the HTML file.
  • ReportResultFontStyle: Refers to the Font Style used specifically in the Execution report.
  • ReportResultFontWeight: This parameter refers to the weight of the font used specifically in the Execution report.
  • ReportFontColor: This is the color of the font used in the report.
  • ReportFontSize: Refers to the size of the font used in the report.
  • ReportPassResultFontColor: Refers to the color of the font used to specify the Pass status of the execution report.
  • ReportPassResultFontWeight: This parameter refers to the weight of the font used to specify the Pass status of the report.
  • ReportFailResultFontColor: This is the color of the font used to specify the Fail status of the execution report.
  • ReportFailResultFontWeight: This parameter refers to the weight of the font used to specify the Fail status of the report.
  • ReportRemarksFontColor: Refers to the font color of the ‘Remarks’ mentioned in the execution report.
  • ReportRemarksFontStyle: Refers to the font style used in the ‘Remarks’.
  • ReportRemarksFontWeight: This parameter specifies the font weight applied to the ‘Remarks’ mentioned in the report.
  • ReportTableHeaderFontColor: Refers to the font color used in the ‘Table Header’ in the report
  • ReportTableHeaderFontStyle: Refers to the font style used in the ‘Table Header’ in the report.
  • ReportTableHeaderFontWeight: This parameter specifies the font weight applied to the Table Header in the report.
  • ReportTableHeaderFontSize: Refers to the font size used in the Table Header in the execution report.
  • ReportTableHeaderBackgroundColor: Refers to the background color of the Table Header.
  • ReportTableBorderColor: This is the color of the table border.
  • ReportTableRowColor: Refers to the background color used in the table row.
  • ReportTableAlternateRowColor: Refers to the background color of the alternate rows in the table.
  • ReportHeaderTextFontColor: This parameter specifies the font color of the text mentioned in the report header.
  • ReportHeaderTextFontStyle: Refers to the font style used in the text of the report header.
  • ReportHeaderTextFontWeight: Refers to the font weight of the text used in the report header.
  • ReportHeaderTextFontSize: Refers to the font size of the text used in the report header.
  • ReportHeaderValueFontColor: This parameter specifies the font color of the values mentioned in the header of the report.
  • ReportHeaderValueFontStyle: Refers to the font style of the values mentioned in the header of the report.
  • ReportHeaderValueFontWeight: This parameter is used to specify the font weight of the values mentioned in the header of the report.
  • ReportHeaderValueFontSize: Refers to the font size of the values mentioned in the Header of the report
  • ReportTestCaseBackgroundColor: Refers to the background color of the test case report.
  • ReportTestCaseStatusWeight: This parameter specifies the weight of the test case status.
Experience hassle free code less test automation

Contact us

TAGS is developed and maintained by Think Future Technologies Pvt Ltd.
If you need any support for implementing your test suites with TAGS.

Contact here


Think Future Technologies Private Limited
12th Floor,
JMD Regent Square
Gurgaon - 122001
Haryana, India

info@tftus.com

+91 124 2807000
+91 124 4290565
+91 124 4290566
Close
Close



Thanks for showing your interest in tagsframework. Link to dowload tagsframework have been sent successfully to your inbox.
OOPS...Some error occured. There might be some network issue. Please try again after some time or contact support for further assistance.