Skip to main content

Description

  • Application to run the Robot Framework Test From the File System with following features.

  • Group Robot Test Cases from different Folders and Group them in batch.

  • Search Test using Robot Tags

  • Run/Track the batch execution status in real time.

  • Bookmarks your frequently used test sets to create batch easily.

  • Run Robot Batch in multiple threads to seed up the execution.

  • Designed to suite Mobile and Web test Automation in mind.

  • This application is written in Python 3.7. Not tested for Python 3.8

  • Can be integrated with Microfocus ALM Authentication.

  • Download the Historical data in csv format.

  • Dashboard for Historical Data (e.g. Test Executions)

Author

Mandeep Dhiman

Installation Requirements

Installation

Using pip

The recommended installation method is using pip

pip install robot-executor

To run the Application, Run following in Terminal/Command

roboapp

How to Create a Batch

How to Create a Batch

How to Run a Batch

How to Run a Batch

How to Create a BookMark

How to Create a BookMark

Statistics

Statistics Demo

ALM Authentication Configuration

This Application comes with ALM Authentication. By Default this is feature is disabled. To enable this feature, Select ‘Options->Use ALM’ from the Options Menu. Note: In order it to work, Make sure you are setting ALM URL from ‘Options->Preferences’ Menu.

Usage

  • Browse to base Robot Framework Project Location Folder.

  • Search the Test Cases by Browsing to different Folder.

  • You can also Search Test by Tags.

  • From the Search Results Add the Test cases to the Batch.

  • Click on Create Batch.

  • Fill in the Required Batch Details Create a Batch

  • Once Batch is Created, Go to Batch Monitor.

  • Right Click the batch and Click Start to Start the Test Execution.

  • Application do not allow to overwrite existing bookmark.

  • If you really want to updated exiting bookmark, then use admin password (Pr1y@)

Note:

Information Provided on Create batch form is exposed as Command line variables to robot Test. So values in these fields can be used in the Robot Test as Variables. Read Setting variables in command line

Here is the Mapping of fields to variable names.

  • Language => ENV_LANGUAGE

  • Test Plan Path => ALMTestPlanPath

  • Test Lab Path => ALMTestLabPath

  • Test Set Name => ALMTestSetName

Mobile Specific Mapping:

  • Select Device / Browser => ENV_DEVICE_UDID

  • Select Server=> ENV_MC_SERVER

  • User Name => ENV_MC_USER_NAME

  • User Password => ENV_MC_USER_PASS

Browser Specific Mapping:

  • Select Device / Browser => ENV_Browser

  • Select URL => ENV_URL

If you are using Microfocus’s ALM Login Form then following variable will be exposed:

  • AlmUrl

  • Name => almuserid

  • Password => almuserpswd

  • Domain => almdomain

  • Project => almproject

Project Contributors

Know Bugs

  • Sorting in Scripts Table

Robot Framework Version Support

robo-executor Version

robotframwork Version Supported

v 0.1.1

v <= 3.1.2

TDB

v 3.2.2

History

Version

Features/enhancements

0.1.1 - 0.1.2

Minor Documentation fixes. Requirements updated.

0.1.0

Added Options Menu, Bug Fixes

0.0.9

Clone Batch Feature, Fixed Broken RST

0.0.8

Added Mac Compatibility, Sorting For Batch Execution Monitor

Metadata

Release files for robot-executor 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for robot-executor 0.1.2
File Interpreter ABI Platform Actions
robot_executor-0.1.2-py3-none-any.whl Python 3 none any Details for robot_executor-0.1.2-py3-none-any.whl

Release files / robot_executor-0.1.2-py3-none-any.whl

Download URL robot_executor-0.1.2-py3-none-any.whl
Size 43.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9828b94bf38289dc67a2a830b10dda036a7d1914dc92120440031677b86df325
BLAKE2b-256 checksum
How to use checksums
76bd1f5a59d3d87c9d4f62118211d81c4639be0425e0f4be5a7bd0b1ece8f78f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2 requests-toolbelt/0.9.1 tqdm/4.42.0 CPython/3.7.0

Security for robot-executor 0.1.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page