|
Now, let's consider the above table for extraction.
In the UI element the locator configured should give us the number of rows
#### Approach 1 (When we want to decide what needs to be extracted)
Under the properties section. Below Configure the below
***prop.column:Your\_ProductElement = Your\_UIElement / LocatorType:LocatorValue***
***Ex : prop.column:FirstName = la.firstName***
In the above format we can configure all the columns or the column's we require.
#### Approach 2 (When we want all the columns with auto key names)
If you have written a locator which gives all columns . Configure as below.
***prop.columns.locator =*** ***Your\_UIElement / LocatorType:LocatorValue***
The result for the above prop will look like below
Item1 : value
Item2 : value
Item3 : value
With any approach once all the rows has been extracted. It will check for the below prop
prop.nextPage.link : UI Element / Locator Type : Locator Path
If it was configured it will navigate to each active page in the pagination and extracts the data
# Trouble Shoot
Answers to yours questions / Exceptions
How can i extract specific columns from my table
With the approach 1, You can simply configure only the required columns.Refer to [Example](/studio/ui-elements/table/example#approach-1-when-we-want-to-decide-what-needs-to-be-extracted)
Column value was not getting changed. First column value is displaying for all the rest
When writting XPATH for the column locator. Make sure you use the (.) before your XPATH
Reason : (.) mean current node
How can I extract only numeric from the column
Let's support your column value is "QATTS235". And you want the value as 235.
For the column UI element . Configure the extraction property.[Extraction Rules](/extraction-rules)
# form
# toogle\_button
# file
# alert
# Automation
# Objects
| Prop Name | Prop Desc | Rules |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- |
| prop.errormsg:\[workflow name] | Defines customer message for an object by workflow name. When there is an exception on an object, this customer message will be added to the standard message. This will help uses to understand possible actions to take to fix the issue. Mainly used for prerequisite verification | |
| | | |
| | | |
# UI Element
Understanding the UI element - a key component in automated web testing
## What is UI Element?
UI elements are integral part of a web application. They are responsible for interactions between the user and the application.
Refer
UI elements can be uniquely identified by their locators.
A locator is a command that tells QATTS to locate a particular UI element.
## Create a UI Element
### Step by step walkthrough
To add an UI Element follow the below steps
**STEP 1**: Log into QATTS goto **Studio** on the left navigation panel, it directs to new window which will be appearing as shown below.
**STEP 2:** On the right corner Click on "**+**" icon and select **Add UI Element**, it should appear as below.
**STEP 3:** Fill the required details as shown in the below screenshot.
{% hint style="info" %}
while filling **Wait Type** select " Time" and in **Wait Value** add value of at least "3 seconds".
{% endhint %}
* **UI Element Name:** The name could any of the user choice.
* **UI Element Type:** The user need to choose the type of the element such as button, text, file etc.
* **HTML Linking:** User need to define type of linking as xpath or others.
* **Locator path:** Here the locator id need to added.
* **Wait Type:** Here time is the default selection.
* **Wait Time:** Here user can add how many seconds the application searches for the locator.
**STEP 4:** After adding required details and then click on **Save**, the given **UI Element name** would be saved in the groups you have selected it in.
### Short video
**Special Locator Options**
DataSetName of custom data options based locators
Locators with Test Data
Locators with Product Element Label name
# Drop Down
Dropdown or Select is a special input type. Unlike standard test box or button we need to perform multiple actions to select a value from a drop down.
Actions to be performed:
1. Click to activate/display the select options
2. Type a Selection Phrase to narrow your results ( Only for dynamic/suggested drop downs. E.g. Google Search is a suggested Drop Down)
3. From the drop down list select a value of your choice
**How to configure?**
Main locator info of the UI element must be pointed to activate/display drop down selection. Usually to click on the container to activate drop down recommendation
Add property **tagName** with value as locator for item selection. For example, if you are selecting a state Florida from the drop down, and all the states names are in span tags, then your locator will be //span\[text()="Florida"].
# Radio Button
| Prop Name | Prop Desc | Prop Rules |
| ---------------------- | ----------------------------------------------------------------------------- | ---------- |
| attName.selected | Element attribute name that have property to define if the option is selected | |
| attName.selected.value | Element attribute value that tells if the option is selected | |
# Multi Elements
There are 2 options available.
Multi Elements
Multi Element with Values
| Prop Name | Prop Desc | Prop Rules |
| ----------------- | -------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| clearBeforeSelect | Before selecting items based on selection, all check boxes will be unselected if they are selected | Boolean (true/false)
Default is false
Only applicable if multiElementType is check box
|
| multiElementType | Type if item that we are dealing with multi selection | checkbox/select |
| groupItemsLocator | Locator to find all the items in the group | Only xpath locator is supported |
| singleItemLocator | Locator to identify single item in the group. To pass item value use ${ItemName} in the locator | |
# table
Table is ready to use component for extracting data an UI table
Table in web application is very important and complex structure holding lot of data. To simplify extracting data from a complex table, qatts have inbuilt component. Just need to config locators of the table, headers, columns and rest of it is magic created by our engineers.
Based on your scenario you can configure properties for quick results:
* Extract selected Columns only and Map to Product Element
Use prop.column:\[Product Element Name] property to define each column and respective product element
* Extract columns without product element definition
*
\>>Extract selected Columns and Map to Product Element
**Locator Type & Path must be given for row array. Not to the table. Column locator has to be relative to row.**
Use below advanced props for table element type
| Prop name | Description | Options |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| prop.column:\[Product Element Name] | Locator for respective Product Element or UI Element. For the product element name in the prop value, give locator info. Locator Info contains locator type and locator path with colon as delimiter | prop.column:First Name ( First Name is product element)
prop.column:ZipCode (ZipCode is Product Element)
Locator Info Syntax
\[locator type]:\[locator path]
|
| prop.columns.locator | Generic locator to each cell. Use columnIndex variable in locator to make it dynamic | if this property is given, it will ignore individual prop.column:\[Product Element Name] |
| prop.column.key | Typical table data will be hold data of an entity. For example a table will hold list of employee. And each row will hold information of an employee. So for employee key field that represent unique employee such as emp id or name etc. Key field for the data set that table data is representing. This is optional and but will be useful in getting the Data from array and display | A valid product element |
| prop.table.noDataElement | Locator to check if table don't have any data. if the element exits, its assume that data doesn't exists in the table | |
| prop.nextPage.link | Locator info of the web element that navigates to the next page. | Optional Field. Locator to be specified as \[locator type]:\[locator path] |
# form
Form UI Element helps doing actions on the complete HTML Form.
**ExtractData**
Extract data for form element will help get all the form data without much configuration.
Use below properties to extract data from various fields on the forms. All form elements may not be same. When they are not same we can't apply same rules for all the fields. Form elements let you a set of properties for each set of fields. For example all text boxs will have same properies, an
| Prop Name | Prop Desc | Prop Options/Info |
| ------------------------------------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| formData.set.\[setIndex].locator | A common Locator for a group form elements | Generally you can define as input or textarea |
| formData.set.\[setIndex].attName | Element attribute value to used for the name of the data of the field | name or id |
| formData.set.\[setIndex].attNameExtraction | Extraction rules that need to be applied on the extracted attName | [Extraction Rules](/extraction-rules) |
| formData.set.\[setIndex].attValue | Element attribute value to used for the value of the data of the field | value or text |
| formData.set.\[setIndex].attValueExtraction | Extraction rules that need to be applied on the extracted attValue | [Extraction Rules](/extraction-rules) |
| formData.set.\[setIndex].dataType | Data type of the data that is there for the field | string,data,number |
| props.page.contentCleanExp | ExtractionRules to clean up dynamic codes | Optional fields[Extraction Rules](/extraction-rules) |
| duplicatesAction | When form have duplicate AttNames what action to be performed | Default option: override
Options:
override
exit
|
# Product Element
Product elements are the data variables in QATTS
## What is Product Element?
Product elements are the data variables in QATTS. They carry the test data to execution engine during test execution.
They have a tight bonding with UI elements. Which means, every product element is associated with a UI element.
## Create Product Element
### Step by step walkthrough
To add an Product Element follow the below steps
**STEP 1**: Go to **Studio**, it directs to new window which will be appearing as shown below.
**STEP 2**: On the right corner Click on "**+**" icon and select **Add Product Element**, it should appear as below.
**STEP 3**: Fill the required details as shown in the below screenshot.
{% hint style="info" %}
Selecting the Group details is mandatory.
{% endhint %}
* **Product Element Name:** The name could any of the user choice.
* **Label Name:** It should be similar to the given product element name.
* **Product Element Type:** There are various fields to choose from input,output,action, custom, page.
* **UI Input Element Name:** Add the UI Element you want to connect it from the drop down selection.
* **UI View Element Name:**
* **Data Type:** Choose the type of data as string, boolean, Integer and others.
* **Database Column Name:**
* **Sequence**:
**STEP 4**: After adding required details and then click on **Save**, the given **Product Element** name would be saved in the groups you have selected it in.
### Short video
{% hint style="info" %}
**Note**: The Product Element Name should be same as the excel sheet headings.
{% endhint %}
# Advanced Data Types
QData
QArray
QStringArray
QIntegerArray
# QIntegerArray
Stores an array of Integer values. Can be constructed with String value separated with delimiters
| Prop Name | Description |
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| delimiter | Predefined Delimiters: comma, dot, hash, hyphen
delimiter.dot
delimiter.hash
Custom Delimiter: must be defined in square brackets. Some examples:
delimiter.\[and] word and is delimiter
delimiter.\[break by] word break by is delimiter
delimiter.\['] character single quote is delimiter
|
# QStringArray
Stores an array of String values. Can be constructed with delimiter
| Prop Name | Description |
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| delimiter | Predefined Delimiters: comma, dot, hash, hyphen
delimiter.dot
delimiter.hash
Custom Delimiter: must be defined in square brackets. Some examples:
delimiter.\[and] word and is delimiter
delimiter.\[break by] word break by is delimiter
delimiter.\['] character single quote is delimiter
|
**Methods**
void addItem(String strValue)
String removeAt(int index)
boolean remove(String strValue)
String getItemAt(int index)
QStringArray getItems(String matchDataName,String prefix)
boolean contains(String strValue)
boolean containsWithStr(String contstr)
boolean endWithStr(String contstr)
boolean startsWith(String prefix)
boolean isSorted(String orderBy)
Integer getSize()
boolean isEmpty()
String toJson()
String toJson(Object keyName)
String\[] toStringArray()
String toString()
boolean doAssert(TFStepContext tfStepContext,String fieldName,QStringArray targetList)
# QArray
**Methods**
* void addItem(QData qData)
* QData removeAt(int index)
* boolean remove(QData qData)
* QData getItemAt(int index)
* QData getItemByKey(String keyValue)
* QData getItem(String matchDataName,Object matchObj)
* QData getItem(String matchDataName,String operator,Object matchObj)
* QArray getItems(String matchDataName,Object matchObj)
* QArray getItems(String matchDataName,String operator,Object matchObj)
* QStringArray findMatchingItemStr(String matchDataName,QStringArray keyArray,String targetDataName)
* QIntegerArray findMatchingItemInt(String matchDataName,QStringArray keyArray,String targetDataName)
* QArray filterData(String inExp)
Filter Data is used to extract data with an expression.
Some examples:
| Expression | Description |
| ----------- | --------------------------------- |
| 1,4,6 | Returns 1st, 4th & 6th objects |
| 1-3,5-7,10 | Returns 1,2,3,5,6,7 & 10 |
| ItemA,ItemB | Retuns key matching, ItemA, ItemB |
Note: if the item in given position or with matching key, exception will be thrown.
* boolean hasItemWithKey(String keyValue)
* Integer getSize()
* boolean isEmpty()
* String toJson()
* String toJson(String keyName)
* QData toQData(String keyName,String valueName)
* void invokeDataModifiers(TFStepContext tfStepContext,TFProductElement tfProductElement)
* boolean doAssert(TFStepContext tfStepContext,String fieldName,QArray targetList)
* double sum(String sumDataName)
* double sumIf(String matchDataName,Object matchObj,String sumDataName)
*
# QData
QData is a data structure which holds data in name:value pairs.
**Data modifiers**: After reading data from any source such as Excel Smarty, Test Data Sheets, API, Database, modifiers will be activated. Qatts has rich library of modifiers defined. On a dataset (QData) many modifiers can be configured to operate in sequential batches. Modifiers has to configured using product element properties.
Property name syntax: modifier.batch**\[number]**.**\[Source Data Name].to.\[Result Data Name]**
**Source Data Name:** Source Data Name is the data key name on which data modification has to be done. if the data value is empty modifiers will not be executed.
**Result Data Name:** Result Data Name is the data key name in which result of the modifier will be saved.
**Batch Number:** In some cases modifier has to be operated in a sequence. Use incremental numbers with prefix **batch**. All modifiers in a batch will be executed in any order.
Property value syntax: **convertTo**:delimiter.\[Delimiter String/Char]
**Date Conversion:** Converting basic data to advanced data types
Expression to use: **convertTo**:delimiter.\[Delimiter String/Char]
Predefined Delimiters: comma, dot, hash, hyphen
Custom Delimiter: must be defined in square brackets. Some examples:
**`delimiter.[and]`**` ``word and is delimiter`
**`delimiter.[break by]`**` ``word break by is delimiter`
**`delimiter.[']`**` ``character single quote is delimiter`
**Moving Data**: Moving data from one element to another element.
Expression to use:
**moveTo**:keyName.\[Child Column Name]:keyValue.\[Child Column Data]
Methods
String getKey()
boolean isEmpty()
boolean containsValue(Object object)
boolean hasDataFor(String dataName)
Integer size()
String\[] getKeyNames()
void setValue(String dataName,Object dataValue)
Object getValue(String dataName)
String getValueAsString(String dataName)
Integer getValueAsInteger(String dataName)
Double getValueAsDouble(String dataName)
Boolean getValueAsBoolean(String dataName)
QData getValueAsQData(String dataName)
String dump()
String toJson()
String toJsonArray(String keyName,String valueName)
# Basic Data Types
Answers to yours questions / Exceptions
# API
Step by step walkthrough on how to add API
## Step by step walkthrough
To Add API kindly follow the below steps
**STEP 1:** Go to **Studio** on the Left Navigation, it directs to new window which will be appearing as shown below.
**STEP 2:** On the right corner Click on "**+**" icon and select **Add API**, it should appear as below.
**STEP 3:** Fill the required details as shown in the below screenshot.
The following is the detailed explanation for adding API details.
* **API Name**: The Name of the API need to be filled ( it could be any name of your convenience).
* **Description**: Mention in detail the project or what type of testing is to be conducted.
* **Type**: It consists of two testing methods -SOAP, REST. Choose according to your need.
* **Select Group**: select the group name which you prefer to conduct the test on.
* **END Point Url**: Add the URL of the source which you are conducting the test.
* **Methods**: POST, GET, PUT, HEAD, PATCH, DELETE, OPTION, TRACE - need to choose one of these methods according to the Testing requirements.
**STEP 4:** Click on **Save** to save the details you have entered.
## Short Video
# Query
Add Query write Queries on different Databases without much needed additional system files and code to execute the query
## What is Query in QATTS?
**Add Query** write Queries on different Databases without much needed additional system files and code to execute the query. Its functionality is to execute the SQL queries on the Database. Normally, if you want to execute a query on the database you have to install a Database tool to perform the tasks. such as installing a Database as Oracle Db or MySQL.
## Step by step walkthrough
To add Query follow the below steps.
**STEP 1**: Click on **Studio** on the Left Navigation Panel, it directs to new window which will be appearing as shown below.
**STEP 2**: On the right corner Click on "**+**" icon and select **Add Query**, it should appear as below.
**STEP 3**: Fill the required details as shown in the below screenshot.
* **Query Name:** The name could be any of the user choice.
* **Description:** Describe the action of the query.
* **Alias Name:**
* **Query:** Here user can write the query, it could be of any depending on the requirement.
**STEP 4**: After adding the required details click on Save and the data will be added in the Group you have Selected.
## Short Video
# Smarty
Smarty is a predefined words or functions that are used in the Action class.
## What is Smarty?
**Smarty** is a predefined words or functions that are used in the **Action class**. For example while testing, If you have to read OTP of an email for 'n' number of times, Instead of writing down the code each and every time you can use the predefined word such as "**email:Reads OTP**", where the action that needs to be taken is already written in the library files.
#### Predefined Smarties
[File: Reads File Data](/automation/objects/smarty/file-reads-file-data)
Email: Read OTP
EmailRead
EmailSend
Capcha
Site Scan
Excel: Read Data from Excel File
Msg Publish: Push message to Published Topic
## Step by step walkthrough
To add Smarty follow the below steps.
**STEP 1**: Click on **Studio** on the Left Navigation Panel, it directs to new window which will be appearing as shown below.
**STEP 2**: On the right corner Click on "**+**" icon and select **Add Smarty**, it should appear as below.
**STEP 3**: Fill the required details as shown in the below screenshot.
* **Smarty Name:** Name could be any of the user choice**.**
* **Description:** Describe the function of the smarty.
* **Smarty Type:** Specify the type of smarty you want to add from the drop down box.
**STEP 4**: After adding the required details click on **Save** and the data will be added in the Group you have Selected.
## Short Video
# Excel: Read data from excel
Reads data from an excel sheet and gives output as QArray or QData based on config
| Param Name | Param Desc | Default Value |
| ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| fileName | Location & Name of the file | Assume that file is in the Agent Data Folder |
| sheetName | Excel Sheet from which data must be read | Mandatory Field |
| dataElementName | Name of the Product Element defining the data structure | Valid Prodcut Element with data type QData |
| dataType | Represent the type of data that you are reading. Select one of the options. \[multiRow, keyValue] | No Default |
| firstRow | Starting row from where the data must be read. For example if the data start from first row, give 1. Remember to match with the row no in excel | 1 |
| endRow | Ends reading when the excel row no is greater then given endRow value | Number. Optional.
Will read until the end of the row if endRow is not given
|
| firstColumn | Starting column from where the data must be read. For example, if the data start from column A, give 1 | 1 |
| firstRowHasColumnHeaders | When true smarty will read column names from the first row of the excel. All the column names must be defined a product elements. When false, it will take column names from the columnNames property. if a column name is not defined as product element, that column will be skipped from reading | false |
| columnNames | Column name will be mapped to the product elements. Specify column names separated with comma | No default |
| keyColumnName | Specify keyColumnName if data is represented with single field. This is very helpful when doing find on the row on QArray | |
| toClipBoard | Copy's data to system clip board | Boolean. True/ False
Default is false
|
| adjustColumnData.batch\[Number]:\[columnName] Column procesing is done based on batch no sequence | 1) Converting String with delimiter to QStringArray
Expression to use:
convertTo:delimiter.\[Delimiter String/Char]:dest.\[Dest Element Name]
Predefined Delimiters:
comma
dot
hash
hyphen
Custom Delimiter: must be defined in square brackets. Some examples:
delimiter.\[and] word and is delimiter
delimiter.\[break by] word break by is delimiter
delimiter.\['] character single quote is delimiter
2) Moving Another column data as child object
Expression to use:
moveAsChild:keyName.\[Child Column Name]:keyValue.\[Child Column Data]
| Optional. Define for columns that need adjustment |
# File: Reads file Data
Reads contents of a file and give data in various formats. Data will be stored in configured bulk param
| Param Name | Param Desc | Default Value |
| ------------ | ------------------------------------------------------------------------------------- | -------------------------------------------- |
| fileName | Location & Name of the file | Assume that file is in the Agent Data Folder |
| outputParam | Bulk Param name to store the content of the file | SmartyName |
| outputFormat | Format in which data need to be stored in bulk data. Options: bytes, base64,jsonArray | bytes |
# EmailRead
EmailRead smarty reads email recent 10 emails from the mail box and filter them based on match criteria.
| aliasName | Email configuration is done in deployment. Aliasname that you want to use for this configuration | Must be a defined alias name from deployment |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| mailServer | Type of Mail server that you are connecting to. For popular mail server we have predefined props that will ease off configuration | Options: office365,gmail |
| protocol | Mail Access Protocol | Options:imaps,smtp,pop3s,pop3 |
| host | Host name to connect to the mail server | Examples:
outlook.office365.com
|
| port | Port no to listen on | |
| domain | Domain Name to access mail box | Optional. Mostly required if you mail server is linked to your active directory |
| username | Username to access mailbox | |
| password | Password to access mailbox | |
| sharedMailbox | Mailbox address of shared mailbox that you want to access | Optional |
| folder | folder in the mail box from which you want to fetch email | Optional: Default: Inbox
Example: Inbox/orders
|
| matchCriteria | Matching text in subject or body.
Expression format: \[fieldName]:\[operation]:\[value]
Supported operators: contains , equals Logical Operators: AND / OR (Make sure to give before and after Logical operators
| Simple Eg: body:contains:Ram
With Dynamic Value Eg: subject:contains:${FirstName}
With Complex Logical Operation Eg: body:contains:Ram AND subject:equals:Inviated
|
| matchOptions | Option to return single item or all | Default: firstOnly
Options:firstOnly,all
|
| extract.field | Message Data field from which information to be extracted | Message Fields: subject,body,receivedDataTime,fromEmail,fromName,toEmails,toNames,ccEmail,ccNames,bccEmails,bccNames |
| extraction.operation | Extraction rules to be applied on the message field | Refer to [Extraction rules](/extraction-rules) |
| | | |
# EmailSend
# SiteScan
Site Scan is very powerful utility to test websites with dynamic content. It scans complete website and checks for broken link, compares it with previous content and many more.
{% file src="/files/oYYJL3fqGBuYfsie44uJ" %}
Site Scan File Template
{% endfile %}
Argument Name: Mode
Multiple options can be given with comma separation.
Example Options:
* saveContent -> Saves content of the site to task folder
* scanOnly -> Scans complete websites and extracts information
* sample -> Used for dry run. Will extract first 10 pages and its Childs
* sample:50 -> Used for dry run. Customize number of pages in the sample. Will extract first 50 pages and its Childs
* PageValidations -> Validates all the pages with w3 standards
* SpellChecks -> Performs spell check for new & changed pages and will be added to the site scan report
* ConsoleErrors -> Extract console error after each page load and logs in ConsoleError sheet of site scan report
| Prop Name | Prop Desc | More Info |
| -------------------- | ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| props.page.checks | Active tag names to checked | Default Options: link:src,link:href,img:src,a:href |
| props.page.element | Check based on an element. Give UI Element name | Links to product element. To use this props.page.checks must be set to "**custom**" |
| baseURL | URL on which we are performing the scan | This must a valid URL. Main URL or can give sub domain |
| cdnURL | List URLs of CDN | multiple CDN urls can be by comma separation |
| props.page.include | Only matching URL to be included | startsWith:\[phrase in the URL]
endsWith:\[phrase in the URL]
regex:\[expression]
contains:\[phrase in the URL]
|
| props.page.exclude | All matching URL's will be excluded | same as include rules. multiple can be given with comma separation |
| inputSiteData | File of approved site scan data | Site Scan Excel file format
File must be in Test Data folder
|
| defaultMissingImages | List of default missing images | Multiple image path can be given as comma separated |
| ignoreChildPages | When true, scan will not check for any child pages | Default is false |
| ignoreSiteMap | When true, scan checks for skips reading the siteMap xml file | Default is false |
| scanCheckType | | FirstOccurance
AllOccurance
|
Compare Site Scan
{% file src="/files/XPTAba1EZqfgHoCU1dVk" %}
Base Scan Template Excel
{% endfile %}
When performing site scan, it is very important to compare and drive test based on previous result. Run site scan once to extract data from the website. This will be used as reference point hence forth. In addition to extracted site scan data, Compare Site scan data must have extra columns, A**ction** & S**tatus**.
Action Values:
* spellcheck
* brokenlinks
# PDF Utils
The PDF Utilities is responsible for comparing and extracting information from PDF files. It provides functionality to compare two PDF files, extract text from a PDF file.
| Property Name | Property Value | Description |
|---|
| StartPage | 1 | The starting page number for comparison/Extraction |
| EndPage | -1 | The ending page number for comparison/Extraction |
| PDFAction | -- | The action to be performed on the PDF files. Available options: "compare", "ExtractText" |
| File1 | Value can be provide either in expressions (td:fileName, ud:fileName) or absolute path | The path or location of the first PDF file for comparison / extraction |
| File2 | Value can be provide either in expressions (td:fileName, ud:fileName) or absolute path | The path or location of the second PDF file for comparison / extraction |
| TrimWhiteSpaces | Default : false | Flag to indicate whether to trim white spaces in the PDF files |
| HighlightDifference | Default : false | Flag to indicate whether to highlight differences in the PDF files |
| DifferenceImageColor | Default : MAGENTA | The color code (e.g., #FF0000) for highlighting differences in the PDF files |
| CompareAllPages | Default : false | Flag to indicate whether to compare all pages of the PDF files |
| CompareType | -- | The type of comparison. Available options: "visual", "text" |
| ExcludeRegexPattern | -- | Regular expression pattern to exclude specific text during comparison |
| fileName | Value can be provide either in expressions (td:fileName, ud:fileName) or absolute path | The path or location of the file
Note : Only when PDF Action is "ExtractText" |
| ExtractionOperation | Refer to : Extraction Rules | Given extraction operation will be applied to the extracted text
Note : Only when PDF action is "ExtractText" |
# New Group
New group is created for a new project or new web page, under which Product Elements of that web page and UI Elements of that web page comes under this group
## What is New Group?
**New group** is created for a new project or new web page, under which Product Elements of that web page and UI Elements of that web page comes under this group. New group is created mostly based on the Functionality.
## Step by step walkthrough
To create New Group Kindly follow the below steps
**STEP 1:** STEP 1: Goto **Studio** in the Agent level, it directs to new window which will be appearing as shown below.
**STEP 2:** On the right corner Click on "**+**" icon and select **New Group**, it should appear as below.
**STEP 3:** Fill the required details as shown in the below screenshot.
* **Group Name:** The name could be any of the user choice.
* **Group Description:** Describe the purpose of the group.
**STEP 4:** After adding required details and then click on **Save**, the given **Group Name** would be saved and it should be displayed in the Groups as shown below.
## Short Video
# Test Case
A Test Caseis a particular web page, with different web elements
## What is Test Case?
A **Functionality** is a particular web page, with different web elements. Here we connect the test data (excel File) in the functionality which is related to the web page.
## Step by step walkthrough
To add a Functionality kindly follow the below steps:
**STEP 1**: Click **Studio** on the Left Navigation Panel, it directs to new window. On the left corner Click on "**+**" icon and select **Add Functionality**, screen should appear as below.
**STEP 2**: Fill the required details as shown in the below screenshot.
* **Functionality Name:** The functionality name could be any of the user choice.
* **Functionality Type:** Select the type from the drop down as Web, API or Function depending on the requirement.
* **Testcase Excel File Name:** The Name given to the file should be same as the test data.
* **Testcase Excel Sheet Name:** Give the sheet name of the test data.
* **Description:** Write the description what this functionality is for.
**STEP 3**: After adding required details and then click on **Save**, the given **Functionality Name** would be saved in the Feature you have chosen in.
## Short Video
{% hint style="danger" %}
Here the Excel file name and sheet name should be exactly same as the it is used in the test data**.**
{% endhint %}
# Function
Function is a reusable block of script code. Function can be called in a test case with executeFunction method. To avoid writing loops in your script you can use function with data table or a query.
You can pass data or data expression for any argument
# Data Table
Data Tables hold data set similar to excel sheet/database table. Typically used to hold configuration or a common data set that may used across multiple test cases
Data Table Access with Expressions
With Direct Row Number: \[Data Table Name]:row no eg: Persons:2
With Multiple Row Numbers: \[Data Table Name]:row no1, Row no 4, row no 5 eg: Persons:1,4,5
With Multiple Row Numbers with range: \[Data Table Name]:row no1 - row no 5 eg: Persons:1-5
# Execution
# Test Case
A specification of input, a set of procedure, desired output is all part of a Test Case.
## What is a Test Case?
A specification of input, a set of procedure, desired output is all part of a Test Case.
For each functionality a excel sheet is linked and whenever a new test cases are added user have to click on the sync button or else newly added test cases in excel sheet will not be synced into the QATTS system.
Here in this section you can check the status of the Test Cases.
To search test cases you can click on the **Search Test cases** as shown below.
It opens a new window as shown below where you need to fill the required data and then click on **Search.**
# Clients Summary
It is a mini dashboards to summarize the Test Cases status for each Client
It is a mini dashboards to summarize the Test Cases status for each Client. User can select the client and retrieve Test cases under the selected client. The Client Names are arranged according to selected Product, Code Branch.
User can click on the required client name to display the test cases under a specific Client. The displayed page would appear as below.
# Search and Manage
In this section you will get to know how to search test cases in QATTS.
In this section you will get to know how to search test cases in QATTS. To search test cases you can click on the **Search Test cases** and your screen should be visible as below.
Fill out the following details.
* **Feature:** Select the feature which you prefer to work on.
* **Functionality:** Select the functionality you prefer to work on.
* Test Case Ref:
* Life Status:
* Execution Status:
* Severity:
* **Client:** Choose the required client for the test cases.
* Approver By:
* Action By: User who is executing the test case.
* Engineer By: user who has created the test case
* TMS id: Here user need to fill the Jira ticket reference number
* TMS Status:
And click on **Search**, your desired test cases will be displayed.
# Context Parameters
# Details by Functionality
The Test cases are arranged according to the functionality name. User can change the test cases by changing the Product, Code Branch and Client.
The Test cases are arranged according to the functionality name. User can change the test cases by changing the Product, Code Branch and Client.
If we go further into the page you can see and Erase and Sync option.
* **Erase**: By clicking user erases all the test cases. Use only if necessary.
* **Sync**: It syncs all the recently added data in the excel sheet to the QATTS.
User can narrow down the test data by selecting a feature.
## Short Video
# Sync
Sync helps you to update your recently edited Test case data.
**Sync** helps you to update your recently edited Test case data.
To understand let us drive in a scenario, If an user have tested couple of test cases and not happy with the result and added few more test cases in the excel sheet. User can just click on the **Sync** button it retrieves and sync the excel sheet that being recently updated.
By syncing the test data you will be getting the below sync message.
Sync Message tells what files are being updated and also displays the test location of the test cases.
# Test Suite
Test suite is a package that you make for certain groups of test cases
## What is Test Suite?
Test suite is a package that you make for certain group of test cases. Here you can give additional properties in the suite for the required test cases.
Suite is collection of test case that intended to be used to test specified set of behavior.
## Step by step walkthrough
The following steps to be followed to create a **New Test Suite**.
**STEP 1**: Login to QATTS, In the Left Navigation Panel Click on **Test Suites** ----> **New Test Suite** as shown as below.
**STEP 2**: After clicking on New Suite you should be able to see the below screen and fill out the required details.
**STEP 3**: Fill out the following details.
* **Suit Name**: You can give a suite according to your Project
* **Description**: Here write down the steps or what this suite is about.
* **Visibility**: Here you can choose between **Private** and **Public**.
* **Private** - The Suite is visible only to you.
* **Public** - The Suite is Visible all who is working on the same Product.
* **Type**: Here you need to choose between **Automated** or **Manual**, by the name itself you can assume its automated or manual testing.
* **Clients:** Choose which client are performing the Test Cases on.
* **Functionality**: Need to choose the functionality which you want to Test.
* **Test Cases**: You can add number of test Cases you wish to perform.
And Click on **Add** and then **Save**, your suite will be saved.
# Create Suite
Step by step walkthrough on how to create suite
## Step by step walkthrough
The following steps to be followed to create a **New Test Suite**.
**STEP 1**: Login to QATTS, In the Left Navigation Panel Click on **Test Suites** ----> **New Test Suite** as shown as below.
**STEP 2**: After clicking on New Suite you should be able to see the below screen and fill out the required details.
**STEP 3**: Fill out the following details.
* **Suit Name**: You can give a suite according to your Project
* **Description**: Here write down the steps or what this suite is about.
* **Visibility**: Here you can choose between **Private** and **Public**.
* **Private** - The Suite is visible only to you.
* **Public** - The Suite is Visible all who is working on the same Product.
* **Type**: Here you need to choose between **Automated** or **Manual**, by the name itself you can assume its automated or manual testing.
* **Clients:** Choose which client are performing the Test Cases on.
* **Functionality**: Need to choose the functionality which you want to Test.
* **Test Cases**: You can add number of test Cases you wish to perform.
And Click on **Add** and then **Save**, your suite will be saved.
## Short Video
# Test Run
Test Run gives the detailed log of the test cases which are running at present and have completed
## What is Test Run?
Test Run gives the detailed log of the test cases which are running at present and have completed. User can customize test runs search by selecting the Product and Code Branch.
## Step by step walkthrough
To create a Test case follow the below steps
**STEP 1**: Click on the Test Run in the Left Navigation Panel and Select Test Run as shown below.
**STEP 2**: Click on the New Test Run. and Select Automated or Manual depending on the requirements.
**STEP 3**: Fill the following details to execute a Test.
* **Test Run** - Any preferred name to given for the Test Execution.
* **Suite** - The required suite should be selected from the drop down list shown.
* **Deployment Name** - Select the required Deployment Name.
* **Build No**: Select the Build No from the given list.
* **Browser** - Select which browser you prefer to test on, if doing API Select No Browser.
* **Client** - Select the Client Environment.
**STEP 4**: After entering the required details click on **Execute** and your Test results will be displayed.
# Schedule Test Run
# Untitled
# Test Result
Here the test runs results are displayed with the functionality name.
Here the test runs results are displayed with the functionality name.
When you click **Test Result** on the Left navigation Panel the following screen appears.
The above image is segregated by the Name of the Clients, If you click on the Clients it directs to another page displaying all the functionalities where you can check the results of the executed test cases in detail.
# Results by Clients
The Clients are arranged according to selected Product, Code Branch.
The Clients are arranged according to selected Product, Code Branch.
User can click on the required client name to display the test cases under a specific Client. The displayed page would appear as below.
# Results by Fuctionality
The Test cases are arranged according to the functionality name. User can change the test cases by changing the Product, Code Branch and Client.
The Test cases are arranged according to the functionality name. User can change the test cases by changing the Product, Code Branch and Client.
User can narrow down the test data by selecting a feature.
# Build No
Learn how to create a Build
## Step by step walkthrough
To create a Build follow the below steps.
**STEP 1:** On the Left Navigation panel Go to **Settings**---> Click on **Builds.** You can see a **Add Roles** as shown below.
**STEP 2:** Click on Create User and fill out the required details.
**STEP 3:** After filling out the required details, click on **Save** and the **Build No** will be saved and should be visible in the Build Summary.
# Reports
# All Failed Test Cases
All the failed test cases will be displayed in this panel depending on the selected Product, Client and Deployment.
All the failed test cases will be displayed in this panel depending on the selected **Product**, **Client** and **Deployment**.
User can click on the **Result Info** to get more information about the test case results.
# Recently Failed Test Cases
---
[Next Page](/llms-full.txt/1)
