...

Table of Contents

Introduction

• Automatics have support for scriptless automation.
• It empowers the testers and other users to automate test cases without worrying about the coding language.
•  Initially for performing the daily rack team activities they are having around 8 tools which are having different URL’s. Users are having very difficult time to change between the applications and also most of the applications are developed long back and dev rack team is in need of many new functionalities.
• So, as a Automation Tools and Framework development team have combined all the tools functionalities and developed a single tool called Automatics 3.0 which is more focused towards user friendliness.
• The tool is very easy to use by everyone.
Not only the rack team all the other teams
• Anyone who is in need of any type of testing can also use this tool as it is
based on
• Keyword driven.

Targeted Functions:

...

...

• User can

...

Scriptless Automation Overview

•  Initially any one of programming languages need to be known for the Automation or Manual tester for create and test the feature,
• When Scriptless Automation concept came into Automatics 3.0 Tool.
• User can easily be able to create the testscripts test scripts without programming intervention using basic commands in existing methods and Available API's.
• Time saving and whoever doesn't have programming knowledge can easily work with Scriptless Automation.  
• Manual testing team can easily find out the failures inside the scripts and verify the bugs produced during testscript triggering time.
• Rich set of utility APIs available.

Details are available in the below links,

Upgrade Automatics to support scriptless execution

For a partner to upgrade Automatics to support scriptless executions need to be done as mentioned below.

Automatics Orchestration

For a partner to upgrade the 3.0 support in Automatics orchestration Please follow below steps.

1. Upgrade Automatics Orchestration to v3.15 or above since it contains the latest code changes for Scriptless Automation execution. Pull the latest code of Automatics Orchestration.
2. Run the SQL scripts from Automatics_DB.sql file present in the Automatics Orchestration starting from line number 1596. These scripts will help in creating all the new tables that are required for Scriptless Automation execution.
3. Add the new changes from hibernate.cfg.xml file which contains the configuration about the two new tables Automatics Orchestration will be interacting with.
4. Once after the above changes generate a WAR file of Automatics Orchestration and deploy it in the tomcat server. Deployment can also be done using Automatics UI. 
5. Verify whether the deployment is done and updated to 3.15 version.

Scriptless Service

Scriptless Service provide the support of API to required for new UI pages added for scriptless automation in Automatics. Hence setting up microservice is an integral part of upgradation 

Refer Automatics 3.0 Scriptless Service Setup for more details on setting up microservice.

Deploy Dependencies Required for Scriptless Execution

Generic 3.0 APIS are defined in Automatics Core , RDKV-Utils(applicable for rdkv executions) and RDKB-Utils(applicable for rdkb executions). hence latest code of mentioned projects need to be deployed to the articrafts.

Refer Jenkins Deployment Jobs for more details on how to create deployment jobs for the mentioned projects.

Utility Parser

Utlity Parser jobs need to be triggered for Automatics core , scriptless-automation , RDKV-utils (for RDKV executions) or RDKB-utills (for RDKB executions) to scan the 3.0 API details defined in the mentioned projects and updated to Automatics.

Refer Automatics 3.0 Utility Parser Jobs for more details on how to create individual parser jobs for mentioned projects .

Configuration Updation

Add the base URLs of Automatics Orchestration and Scriptless Service application in database, which will help in the communication between one and another. Use 'AUTOMATICS_BASE_URL' and 'MICROSERVICE_URL' as the config names for adding the base URLs of orchestration and microservice in master_config table.

Update urls in Automatics properties

Update below parameters to Automatics properties these urls need to be defined to support 3.0 Executions 

predefined_ds_bulk_url= <Scriptless Service Bsse Url>/addBulkPredefinedEntries

service.base.url=<Scriptless Service Base URL> 

Steps to trigger scriptless test case

• Create a scriptless test case Please refer Automatics 3.0 User Manual#BuildTestCase for more details on how to generate a scriptless test case.
• Once successfully created a scriptless test case Navigate to Manage Scripts page and enable the newly added test case
• After successfully enabling the test case Please refer Automatics 3.0 User Manual#ManageTestTrigger for details on how to trigger the test case.