Open Source Test Automation Frameworks

OPEN Action is an action based Test automation framework for mobile and web, designed by seamlessly integrating multiple open source tools to offer a complete end-to-end test automation solution.

The solution can be extended further for:
OPEN Action

OPEN Action FAQ:

What is Action based test automation framework?​​

Combination of actions on a test object which describes how test lines must be executed. An action is associated with arguments and is defined by a test analyst.

It follows the principles of software testing methodology which are suitable for both manual and automated testing. This method separates the documentation of test cases in excel – including the data to use- from the development of reusable action modules in Java hence, test case construction can be performed by the stronger domain experts – lesser tool / programming skills and Action implementation can be carried out by the stronger tool/programming skill – with relatively lower domain skills. The framework is designed and developed on good development principles and does account for, Reliability | Usability | Efficiency | Maintainability | Portability.

W​hat does OPEN Action provide support for?​
What tools are leveraged by OPEN Action?

Selenium, Appium and Selendroid.

What is meant by end-to-end complete automation solution?

The Solution, OPEN Action provides the capability of test case design, development, Execution and reporting. All the assets developed can be version controlled and easily maintained for parallel execution across multiple releases/environments. If desired the entire test suite can be configured for Continuous Integration (CI) testing to validate the quality of the periodic builds.

What is CI Testing?

Continuous Integration (CI) is the practice, in software engineering, of merging all developer working copies with a shared mainline several times a day. Its main aim is to prevent integration problems.

CI Testing intended to be used in combination with automated unit tests, running them all and verifying that they all passed before the changes are deployed to the users. Organizations using CI typically use a build server to implement continuous processes of applying quality control in general — small pieces of effort, applied frequently.

In addition to running the unit and integration tests, such processes run additional functional static and dynamic tests. This continuous application of quality control aims to improve the quality of software, and to reduce the time taken to deliver it, by replacing the traditional practice of applying quality control after completing all development.

CI Testing Benefits:
OPEN Action Benefits:
Engagement Models: (onsite/offsite)