We utilize the micro service architecture more and more often while developing software nowadays. It allows us not only to speed the development up, but also to make the end product more agile and easy to scale.
A large governmental enterprise that processes a huge amount of various documents has recently approached us. We had to organize the autonomous testing process of key subsystems, which comprise the automated information system. Moreover, we couldn’t use an out-of-box solution (client’s specification), so we had to develop a custom tool that would satisfy the client’s requirements.
Initially we studied the system specification and designed a subsystem cooperation scheme It allowed us to determine the main requirements and formulate the project charter for the future subsystem emulator.
The document processing workflow looked like this:
Subsystem A – it is a transport subsystem that connects all subsystems
Subsystem B, C, D, n – these subsystems, each of which is responsible for processing a specific data set
REST queries are responsible for the subsystem communication.
Here is an example of a subsystem communication:
We’ve developed a user manual for the client during the project.
The testing team has encountered the following problems while analyzing the client’s requirements to the emulator: