The application that you write will be the Client, and you will send HTTP request/response, to the Server. The Client in this instance will act like a "web browser", which is similar to Postman.
I very doubt you can set headers and cookies in MS Edge and Chrome externally. I'm not aware of TC having build-in tools for this. To reuse the authenication, save the authentication key, and then pass this key with its appropriate header, to the next request.
rraghvani wrote:The application that you write will be the Client, and you will send HTTP request/response, to the Server. The Client in this instance will act like a "web browser", which is similar to Postman.
Not sure I understand this part. Where this should be done? What is the step number in my example test?
Does that mean I should login via API, then send HTTP request (what will be request?) with required headers and then launch browser and go through all actions required in my test?
