Lots of systems reusing different JSON schemas, which we need to mock,<\/p>\n
By using JSON schema \/ template files to construct and push custom JSON messages to different systems..<\/p>\n
Here’s where I have reached so for in solving it and the implementation steps:<\/p>\n
Step 1 – Basic structure to push a given JSON file to one system<\/p>\n
Step 2 – Add support for more systems to push messages to<\/p>\n
Step 3 – Create library to take a ‘JSON Schema’ as a template, and fill placeholders with test data values<\/p>\n
The need arises when we have mulitple products to push messages to, all having different JSON message structures,<\/p>\n
For testing these systems, instead of having ‘n’ number of JSON files, one per script, I’m thinkging of having standard templates for each product<\/p>\n
Which will hopefully make it easier to mock test JSON files, and<\/p>\n
Instead of passing the complete JSON, just the template name and a few variable values should do the trick<\/p>\n
Still each script might have a sort of ‘config data’ file, but should be quite homogenous within products<\/p>\n
Any other ways you’ve tried to implement this, or thoughts on this implementation?<\/p>\n
#QSDaily #Automation #MockingData #JSON<\/p>\n
<\/p>\n<\/div>