Banner
Home      Log In      Contacts      FAQs      INSTICC Portal
 
Documents

Tutorials

The role of the tutorials is to provide a platform for a more intensive scientific exchange amongst researchers interested in a particular topic and as a meeting point for the community. Tutorials complement the depth-oriented technical sessions by providing participants with broad overviews of emerging fields. A tutorial can be scheduled for 1.5 or 3 hours.

Tutorial proposals are accepted until:

April 10, 2026


If you wish to propose a new Tutorial please kindly fill out and submit this Expression of Interest form.



Tutorial on
Automated Testing using Robotic Test Framework




Abstract

Abstract
Every software that is developed goes through the user acceptance testing phase. UAT can be time consuming and a cumbersome process.
Generally, UAT involves more than one cycle of testing as bugs raised in previous UAT cycle need to be rested in addition to performing end-to-end UAT testing cycle. In order to reduce the UAT cycle time – UAT test scripts can be written in Robotic test framework


Keywords

Robotic Test Framework, CI/CD, Keyword-driven, test-automation

Aims and Learning Objectives

This tutorial gives an insight to the user how to perform automation testing using robotic test framework

Target Audience

Developers,Testers,Business Analysts, Technical Architects

Prerequisite Knowledge of Audience

The audience shoould know different types of software testing and also should have basic knowledge of programming language.

Detailed Outline

Robotic test framework is an open-source framework. primarily used for acceptance testing, acceptance test-driven development (ATDD), and robotic process automation (RPA)
Its human-friendly and versatile syntax uses keywords and supports extending through libraries in Python, Java, and other languages.
It is a keyword-driven and supports both manual and automated testing of applications. It is highly extensible and can integrate with a range of external tools and libraries.

RTF is highly modular architecture of the robotic framework

Main Use Cases:
Test automation (functional & regression)
API testing
Web UI testing
Acceptance Testing
RPA (Robotic Process Automation)

RTF Architecture
Test Cases: Written in .robot files using human-readable keywords.
Test Libraries: Built-in or external (e.g., SeleniumLibrary, AppiumLibrary, RequestsLibrary).
Keywords: Define actions and logic in test cases. Can be:
Built-in
Library keywords
User-defined
Test Runner: Executes the test suites and generates reports/logs.
Reporting: Automatically generates detailed HTML-based logs, reports, and outputs

Test Case 1 – Webservice Connection

*** Settings ***
Library SeleniumLibrary

*** Variables ***
${browser} chrome
${url} https://demo.nopcommerce.com/

*** Test Cases ***
LoginTest
# open browser https://demo.nopcommerce.com/
open browser ${url} ${browser}
title should be nopCommerce demo store
sleep 10
click link My account
sleep 10

y SeleniumLibrary

*** Variables ***
${url} https://opensource-demo.orangehrmlive.com/web/index.php/auth/login
${browser} Chrome

Test Case 2 – Login to an application/website

*** Test Cases ***
LoginTest
open browser ${url} ${browser}
sleep 10
input text name:username Admin
input text xpath://body/div[@id='app']/div[1]/div[1]/div[1]/div[1]/div[2]/div[2]/form[1]/div[2]/div[1]/div[2]/input[1] admin123
click button xpath://body/div[@id='app']/div[1]/div[1]/div[1]/div[1]/div[2]/div[2]/form[1]/div[3]/button[1]
close browser

Test Case 3 - API Get Request
*** Settings ***
Library RequestsLibrary
*** Variables ***
${base_url} https://reqres.in

*** Test Cases ***
Get_Request
create session mysession ${base_url}
${endpoint} set variable /api/users?page=1/
${response}= get on session mysession ${endpoint}
log to console ${response.status_code}
log to console ${response.content}
#validations
${status_code}= convert to string ${response.status_code}
should be equal ${status_code} 200
${body}= convert to string ${response.content}
should contain ${body} Emma

Running the test scripts from CI/CD (Jenkins)
Installation of the Jenkins server on the local machine
Installing pre-requisite libraries (JRE, Java etc)
Creating Project in Jenkins Server

Running the Jenkins Server

Integrating the test scripts with the Jenkins Server


Secretariat Contacts
e-mail: enase.secretariat@insticc.org

footer