Accenture Products & Platforms (APP) Accenture Health .

Alias Framework Reference Guide3.1.3.models–Provides the metadata files for ABMS, ACSSP, Presumptive Eligibility and Provider Portals. Note that eachapplication requires its own metadata file and each metadata sheet name should indicate the application name.–It is a repository of all web elements. It contains required elements such as Screen Name, Label, FieldName,Type, and Path. The optional elements include isMultiple, Version, Create, WaitTime, Conditional etc.–Refer to the screenshot below as an example for ABMS model:Figure 5: ABMS Model Spreadsheet Example–The elements indicate the following: Screen Name: Shows the web page to which the web element belongs. Note that each screen can haveone or more page mode hence the screen elements will have different Xpaths based on the page mode. Forinstance, view and edit modes for the same screen will have different elements and xpaths. Hence,separate pages are created allowing the elements that go with a view mode to be grouped together and theones with the edit mode to be grouped together.Label: Indicates the label by which the web element is used in the script. For example: First Name. Labelgenerally corresponds to the field name or a short form of a field name on the screen. It is used to explicitlypopulate a certain field in the test script. FieldName: Indicates the web element name by which the web element is used by the data source.“FieldName” is used to link the data sheet (Source Data File) and the current row. In the datasheet, theFieldName is used to identify the data for the given row/field.Type: Indicates the type of web element. For example: button, text, dropdown, checkbox, radio, and link. XPath: Shows the location of the web element on the web page. Wait Time: Indicates the time Alias looks for the web element before failing the script. This is optional. Ifprovided, engine will attempt to identify until the provided wait time. Wait time is mentioned in seconds. Order: Indicates the order in which the web elements are populated on the screen. If not provided, systemwill use the default order of elements in the input file. Mode: Indicates if the given webelement is applicable to all modes or only specific mode below. A- All modes – indicates the given element is visible in both Desktop and Mobile render modes.Copyright 2020 Accenture All Rights Reserved.11

Alias Framework Reference Guide D – Desktop only - indicates the given element is visible only in the Desktop render mode. M – Mobile only - indicates the given element is visible only in the Mobile render mode.Key points to keep in mind when creating a model for an application:–Every line is a unique web element.–Each web element has required properties that should be defined.–It is important to NOT have duplicate web element labels for the same web page. Else the existing label will beoverridden by the new one.–If the screen name has a word popup at the end, it means the screen is a pop up window. For example, ABMSAdd Journal Entry Popup. While populating the data to a pop up screen,, Alias understands to change the viewmode from main window to a popup window.–Web elements that belong to the same page not necessarily need to be in sequence within the model, howeverit is highly recommended.–For screen names, labels, and field names, follow the below syntax rules.3.1.4. Do not use special characters. Only use letters, numbers and spaces. Do not use upper case in the middle of the word. For example: the field name should be written as FirstName instead of FirstName. Do not leave empty spaces in the beginning or at the end of the names.scripts Contains test scripts written in cucumber for applications for which model/object repository data is captured. Steps in the test scripts are written by Gherkin language using syntax such as Given, When, Then, And etc. Let’stake an example of an existing script below called Login.feature:Figure 6: Feature File (Script) ExampleCopyright 2020 Accenture All Rights Reserved.12

Alias Framework Reference GuideLet’s discuss each part of the above example below: Tags – A tag helps to group the script during execution. It helps to identify the category that the script belongs to.Tags are also used to identify the applicable jenkins job that will execute the script. For example, @smoke tag willbe picked up by the smoke Jenkins job. Once the jenkins job is run, the final cucumber HTML report groups thescripts results by tags.@reuse in the above snippet is one example of a tag.Some key points to keep in mind for tags: –Scripts that include the @ignore tag will not be executed.–You can add any amount of tags, as needed. However, it is recommended to review the list of existing tagsbefore you create a new one.–Tags are case sensitive. For example, @Smoke and @smoke are considered 2 separate tags.Feature - Specifies the feature file name followed by the person’s name who created the feature.Note: It is highly recommended to provide as much details for each feature in the recommended format shown inthe screenshot below:Figure 7 Format for Feature Background: Defines the data that the script uses for execution. As per Gherkin language, background is executedeach time before a scenario is executed in a feature file. Note that there can be multiple scenarios in a feature filewhich means the background will be executed multiple times.Let’s look at the below snippet as an example:Figure 8 Format for Background–Background will always include the step that defines the script name. It is recommended to keep the script nameunder 30 characters.–The syntax used such as Then, When etc. are optional, can be interchanged with one another and/or can bereplaced with an asterisk (*).–Background also defines the data source for a particular data set. This is only applicable when the data isneeded to use from the data sheet.Copyright 2020 Accenture All Rights Reserved.13

Alias Framework Reference GuideFor more information on how to define a data source, refer to the instructions defined in How to define a data sourceprocess within the Alias Command Index included in the Appendix section of this document. Scenario: Scenarios are the series of actions that take place in a script execution. Each scenario is independent ofeach other and should be ordered in sequence. You must provide a scenario name following the syntax rulesdefined in the models section above.Below is an example of scenarios in a Login script.Figure 9 Format for Scenario–Scenario name can be written in the below 2 ways: Simple Text ( For example, Preconditions or Close Browser as shown in line 10 and 19 in the abovesnippet) – This is a one-time step in a given feature file. Precondition is a scenario defined in the beginningin order to execute the steps generally needed at the start of the feature and are common to all scenarios.For example: Opening the browser is a step listed under Precondition as it is not required to be executed foreach scenario in a given feature. Text separated by : : (For example, Log into ABMS:: ABMS Login as shown in line 13) – This formatindicates the scenario has reusable components which can be used in other scripts.Scenario naming format with reusable components: Unique Scenario Name : : Unique Reusable Java ClassName The unique scenario name can be used as a step in any other feature file(s), as needed.Copyright 2020 Accenture All Rights Reserved.14

Alias Framework Reference GuideLet’s look how reusable scenario is used in any other feature file:In our above example, Log into ABMS:: ABMS Login is a reusable scenario which is also used in another script. Refer tothe screenshot below for Non Compliance script as an example on how Log into ABMS reusable scenario is used in thisscript.Figure 10 Script Example Using Reusable ScenarioWhen a reusable scenario is used in another script, it is important to know that the background for the original scenario willnot be executed in the other script unless conditions are defined in the other script. Note that the data set used in areusable scenario defined in the original script will need to be also defined in the other script that’s reusing the scenario. Inthe above example for ABMS Login script, ABMS Login Data is the data set used which is also defined in theNon Compliance feature script, as shown in the screenshot below.Note that Alias provides the possibility of providing a different data set name. Refer to How to use datasources in theCommand Index included in the Appendix section of this document.Figure 11: Script Example Using Reusable Scenario Data SetCopyright 2020 Accenture All Rights Reserved.15

Alias Framework Reference GuideBelow are the key reusable components conditions to keep in mind:-The scenario name with reusable components cannot be used in any other script in Alias.-The reusable scenario will be available for use in other script(s) only when it has been successfully executed at leastonce in the original script.-If any changes has been made to a reusable scenario, the updated scenario need to be executed at least once for itto execute it successfully in the other scripts.-Do not re use the reusable scenario in the script it was created.3.1.5.SourceDataFilesThe source data files contain the data files / values used in the test scripts. The data files contain the Field Name, PageName Reference, and the corresponding values.Key points to keep in mind for the source data files structure: The data is separated by the application type. The Field Name column (Column A) is the index of the values. It should never have any empty lines and the lastline should always say the text END. The Field Name column should not have duplicate values and should always follow the syntax rules. In case of multiple scenarios, each scenario is called out in a different column in the data source file and a script foreach scenario exists in Alias. The date pattern used is given below:–#d( 0 0 0 MM/yyyy) – populates today’s day, month and year–#d( 1 0 0 dd/MM/yyyy) – adds one day to today’s day, month and yearFigure 12 Source Data Files Structure2.2.How Database and Web Services Work Together?To use the database, the below key things are required: Database configurations should be properly set up for the specific application environment you want to use.–Configurations should be set up in the env.json file. For example: to use Prod fix 7.3.x environment, add thedatabase driver, database URL, database user and the corresponding password. Alias uses these credentials toaccess the given URL.Copyright 2020 Accenture All Rights Reserved.16

Alias Framework Reference Guide– Currently, JDBC thin driver is the only database driver supported currently.Queries that you want to use should be set up.–To set up the query, include the name of the query and the query in the env.json file. For example: Name: RIDPPrimary Final Decision. The RESPONSE CODE, RESPONSE CODE DESCRIPTION, and theDECISION CODE results from this query. The queries contain the placeholder(s) which will be passed from thefeature or the data file. For example: (Last Name Person 1). This naming convention followed for theplaceholder is (FieldName).–Use a specific command required to execute a query. The below command is used to execute the query.Engine then takes the query and run it against the database URL, and the user provided in the configurationsettings. The result is saved in the context of the active data set.Then execute "QueryName" query–Use a specific command required to validate the contents of the query results. The below command is used tovalidate the query.Then Validate "Response Code" data "RESPONSE CODE" from query resultsIn the above command, "Response Code" is a value provided in the DataSource used, however the"RESPONSE CODE" is the result from the query used and should match the name of the column of what wasreceived.Note: If validation fails, the script fails here. If successful, the script execution continues.To use the Web Services, the below key things are required : A template of the soap webservice request needs to be specified and is dynamically loaded with the passed valuesto hit the soap webservices. The key things for the template that you should keep in mind:–The dynamic variables should end with # in the soap webservice request template file.–Ensure that the variable name specified in the template should match with the variable names in the excel sheetor the captured variables.–For Example: gcd:CaseNumber CASENUMBER# /gcd:CaseNumber –Template xml path : \xmlTemplates–This is located in the ALIAS client project. But the template path can be anything and should include the xml filename in the below mentioned json file.Copyright 2020 Accenture All Rights Reserved.17

Alias Framework Reference GuideJson file for Template path :webService.json, For Example:{"templatePath": e.xml"}}Json File for Endpoint Url :The endpoint URLs are environment specific and should be mentioned in the Env.json. An example of endpoint URLs asspecified in the env.json file is as below:"Prodfix 7.3.x": {"release":"7.3.x","dbDriver": "oracle.jdbc.OracleDriver","applications": {"ABMS": {"appUrl": ","dbUser": "ABMSUSER","dbPwd":"Aust1n"},"SSP": {"appUrl": ,"dbUrl": ser": "ACSSPUSER","dbPwd":"Ch1cag0"},"PE": {"appUrl": ,"PP": {"appUrl": "https://demo.ahps123.com:99

Accenture Products & Platforms (APP) Accenture Health & Public Services Accenture Human Services Suite . Another option is mobile that opens the browser in the emulator mode and is only enabled for the chrome browser. This means if you want to t