Background & Philosophy

JSystem started in 2002 as an in-house project and then was re-written in 2004 as an independent framework. Since its early days customers have implemented test automation projects with it.
The first and most important contribution of JSystem to the development of successful and scalable projects is JSystem methodology which handles automation projects as a software projects.

It may seem obvious but in many places the automation project is just a bunch of scripts that sometimes are not managed with a source control tool, and does not adhere to a design standard. This might work at the beginning of a simple project but once the number of tests grows and the number of people that work on the project grows, the project becomes complicated and adding new capabilities to the project becomes difficult.
The JSystem methodology requires that the system testing automation project is developed using standard development conventions.
Projects developed using JSystem methodology have a standard design framework, based on the four layers of automation.

An additional implication of treating an automation project as a software project is that according to our philosophy “record and play” utilities can not be the basis of an automation project but just a utility in the project used to accelerate project development, thus the JSystem framework is an API based framework.

Fork me on GitHub