Some tips here … yeah, i know, coming from Postman into Katalon can be a bit confusing at the beginning:
With Postman, for every test scenario, you create a request, pre-conditions are initialized into the Pre script and verifications are done into the Test script. So, for a new scenario using the same request (let’s say once you do a valid API call and check for success and for the second you provide wrong data and check for 404 code) you have to create a new request (could be duplicated from the first one)
With Katalon, you have to think up-side-down. You make a single request object, parametrized, and for every scenario you create a TestCase, passing variables accordingly. Verification’s are made in the testcase.
Of-course, you can use same approach like in postman, for every scenario create a request object and use the verification snippets straight in the request object … but using the other way will give you more flexibility and the resulting project will be cleaner, will have less request objects.
Personally i prefer to make only few generic request objects. Let’s say one for GET, one for POST, one for PUT, one for DELETE, fully parameterized, and maybe one more for grabbing the auth token.
For the rest I simply create testcases for each scenario needed and initialize the variables straight from the code (endpoint, header if its changing, body etc)
During the design stage, I just run the auth call manually, copy the token and paste into the Execution Profile in use. When it’s expired, renew it.
Once I have few tescases working, I make a suite, where the first tescase is the one which gets the token and is saving it into the Global Variables > run it.
And so on, for every new scenario, make a new testcase, run it manually, once is working fine, add it to the suite.
You can have also another verification suite where you put only the auth testcase and the new designed … once it’s working fine add the new case into the main suite too.
And more, once you have a full suite with all kind of scenarios (postive, negative, boundary etc) you can duplicate it, keep only the positive tests and use it as a smoke suite, the full one can be used as sanity or regression. With Postman, for this you will have to duplicate the full collection and remove the requests not needed or do some dirty voodoo using
postman.setNextRequest… so I think you can see some benefits here.
Hope this hints will help you to migrate easily. Cheers!