ContributionsMost RecentMost LikesSolutionsRe: Schema validation for offline schemas richiesorry if I wasn't clear We do not have the ability to access the schema through an online url, they are not public facing yet The current way I did it was to write the schema by hand in javascript in postman and then use the postman schema validation to to assert that the response from the postman call matched the schema supplied in code, the 2 postman tests below pm.test("Response is ok(authorized)", function () { pm.response.to.have.status(200); }); pm.test("Schema is valid", function () { const schema = { "type":"array", "items":[ {"type":"object", "properties":{ "Id": {"type":"string"}, "Number": {"type":"string"}, "AK": {"type":"integer"}, "CategoryId": {"type":"integer"}, "Note": {"type":"string"}, "CreatedByUserId": {"type":"string"}, "CreatedDate": {"type":"string"}, "LastModifiedByUserId": {"type":"string"}, "LastModifiedDate": {"type":"string"} }, "required":["Id", "Number", "AK", "CategoryId", "Note", "CreatedByUserId", "CreatedDate", "LastModifiedByUserId", "LastModifiedDate"], "additionalProperties": false }], }; pm.response.to.have.jsonSchema(schema); }); I was thinking I could use a groovy validator to do it and then just get the result and check that Re: Schema validation for offline schemas richie Thanks for the reply, at this stage I don;t have the ability to do any url based schema validation - I am going to need to investigate groovy scripting for a schema Schema validation for offline schemas Hi, in Postman I can define a schema and the assert against that directly - how can I do this in Ready API eg, the schema and then the assert I see ready API has a URL to point to but I can't use it, so was wondering how I do this the same as postman const schema = { "type":"array", "items":[ {"type":"object", "properties":{ "Id": {"type":"string"}, "Number": {"type":"string"}, "AK": {"type":"integer"}, "CategoryId": {"type":"integer"}, "Note": {"type":"string"}, "CreatedByUserId": {"type":"string"}, "CreatedDate": {"type":"string"}, "LastModifiedByUserId": {"type":"string"}, "LastModifiedDate": {"type":"string"} }, "required":["Id", "Number", "AK", "CategoryId", "Note", "CreatedByUserId", "CreatedDate", "LastModifiedByUserId", "LastModifiedDate"], "additionalProperties": false}], } pm.response.to.have.jsonSchema(schema); Thanks Re: Project structure Hey, thanks will have a read. Project structure Hi, I am evaluating ready API as a Postman replacement for our work and have a question around project level variables that need to be generated at some point of the API testing process. I have dates for example Past, Current and Future To get this working quickly I wrote a groovy script that returned the current date I added this step as a test step in the flow, just before the step that needed the date in the API url, all works well However I have many API calls that need the current date or other dates to test things with, so my initials thoughts were 1. Add a groovy script in each place - no not keen, too much work to maintain 2. Do what I did in postman and create the variables before I run any tests and save them as project variables. Just really wanted an idea on how other Ready API users are doing this My initial idea was to make a Test scripts test suite and put the scripts inside there that run as test steps and save the results before any of the other tests run eg Any thoughts, feedback and ideas are all welcome, thanks Solved