There are two types of Test Services:

• Test Support Services (TSSs). Conceived as services that are enabled on demand, they provide additional functionality that can be used during the execution of a TJob. One instance of these services will be created each time a job is executed.
  • ElasTest User Emulator Service (EUS). Service that provides browsers for both manual interaction and automated interacion under the control of tests, by means of starting browsers in containers.
  • ElasTest Device Service (EDS). Emulates the behaviors of the sensors, actuators and smart devices you need to perform your tests.
  • ElasTest Monitoring Service (EMS). Service that allows monitoring the execution of the TJobs and SUTs, in a similar way to the normal mode, but with a greater capacity of configuration.
  • ElasTest Bigdata Service (EBS). Service that provides a computing engine based on Apache Spark to be utilized by tests inside ElasTest, as well as other ElasTest services. It is disposable, meaning that it can be commissioned/decommissioned on demand and scalable, meaning that it can be resized to provide capacity for faster/bigger calculations. EBS enables ElasTest to easily perform operations on huge datasets being stored locally, in distributed filesystems (HDFS) or remote ones (e.g. Amazon S3).
  • ElasTest Security Service (ESS). Service that can be used to detect security vulnerabilities in the System Under Test (SuT).

• Test Engines(TEs). Similar to the TSSs with the difference that a single instance of a Test Engine will be used by all the TJobs configured in the platform.
  • ElasTest Cost Engine (ECE). Service that provides to the users the information to consider the financial of using clouds. Using clouds cost money, in third party clouds you pay for the time and resources you use. As well as in on-premises clouds, you pay for the energy and the hardware resources utilization.