The GenRocket Multi-User Server (GMUS)
Most GenRocket customers install the GenRocket Runtime on their tester’s machines and use the GenRocket User Interface to create test data generation Scenarios.The Runtime is then used to execute test data Scenarios on their tester’s local machines.
Some GenRocket customers, however, want to integrate GenRocket into their test automation framework and hide the GenRocket User Interface from their testers. These customers want potentially hundreds of testers to request test data from within their test automation framework without learning how to use the GenRocket UI.
To meet the requirements of these kinds of large scale, integrated, test automation environments GenRocket developed the GenRocket Multi-User Server or GMUS.
Inside the GMUS Architecture
The GMUS is a shared environment that manages requests and delivery of test data to simplify on-demand test data provisioning for testers. The diagram below illustrates the GenRocket Multi-User Component Architecture. The large blue box represents GMUS software that is installed, on premise, on a server. Green boxes represent specialized components of the GenRocket architecture that work together to perform various functions. Orange boxes represent external users or client applications accessing the GenRocket platform.
A typical GMUS server has 4 Cores and 16GB of memory that is mostly (or totally) allocated to GMUS operations. Internally, the GMUS manages test data requests and spins up multiple GenRocket API instances and multiple Scenarios that are dynamically modified in real time to meet the data requirements of each tester’s test case.
The GMUS guards against scenario collisions when two or more users request the same Test Data Scenario at the same time, and it maintains the “state” of test data to ensure that unique data is delivered when requested for each test. The GMUS also performs load balancing to service all requests from many testers with optimum performance.
GMUS Core Features:
- Integrates with test automation frameworks developed in any programming language
- Both RESTful Web Services or TCP/IP Socket Requests can be used for integration
- Large quantity of users can request test data from a single GMUS
- Simultaneous data requests are load balanced
- API commands can be passed to the GMUS to dynamically generate data on demand
- Record & playback
- Logging
- Messaging
GMUS Implementation
To implement the GMUS customers should work with a trained and certified GenRocket channel partner with experience programming the GenRocket API. The Implementing channel partner will need to at least:
- Integrate GenRocket into the customer’s test automation framework via RESTful Web Services or TCP/IP Socket Requests
- Specify back end API commands that are passed to the GMUS to dynamically configure and run test data generation scenarios
GMUS Example #1
A major insurance company with a home-grown testing automation platform wanted to seamlessly integrate GenRocket into their existing platform. They didn’t want to change their testers behavior – just give their testers a better, integrated test data solution. The GMUS was a perfect solution.
GMUS Example #2
A financial services firm wanted to test their new mobile application across many mobile devices. To fully test their mobile app they needed sufficient volume and variety of realistic data for their tests. By implementing the GMUS they were able to make many simultaneous REST calls to all the mobile phones in their test bed. The GMUS was a perfect solution.