There is any way that, in the verification, has a body as expected?

I want to validate that the same get will always have the same response and for that, I need to have the body  as expected

 

Ideally, would be nice to have the expected a file path to the json

How to handle with this ? 

Hello,

I tried installing the BETA version, however, after installation it only allow me to use it for 30 days trial. Is the free BETA release for Test Studio APIs no longer available? If yes, how much it would cost if I purchase a license? 

 

Thanks & Regards!

Sarah Marcellana

 

I would like to be able to set variables as a step, directly from a string I provide rather than as a result of some other step.

We have custom authorization (signed messages, etc) that require us to have access to the http method type, body, url, and some other things to properly sign each http request. I have this working for the most part but it would be a lot easier if I had access to get the members of a specific request. Maybe putting a code behind directly on a request step would work too? Whatever I'm doing is kind of hacky, that's for sure.

With Postman I'm able to add client certificates (set certificate, set key file, add pass phrase. etc) which in then turn be sent when a request is made to a configured domain. Does the current API test tool allow for similar functionality or can you instruct me on how this can be accomplished. 

I get differing results when running an entire project vs a single test through the command line.    

As an example, if I run as a single test through the command line 17 requests execute in 13 seconds, no issues.  Running that same test in a project, the first requests takes 60 seconds, and hits the timeout limit. 

Hello,

Is it possible to run API tests on remote test server without buying licence with Test Studio and Test Studio runtime. In one webinar about 2016 new features I heard that API test tool is free BETA which seems to continue till now. Or I need at least one Test Studio runtime licence for $349?

Thank you.

Best regards,

Tomas Kruzik

Any recommendations to deal with timeouts?  

I have some tests that return results when run independently, but when run in a suite, it overloads the server, and a cascade of timeouts occur.  

I've tried using a wait step at the beginning of each test case to allow the server some recovery time, but I feel like there is a better way to do this.  

Is there a way to mark tests as continue on failure, similar to regular Test Studio functionality?  

Is it possible to setup a coded step to run another test before continuing. 

Use case is: There are some setup tests that need to be ran before other tests.

A coded step to call those tests first would be ideal, is there a solution for this?

Thanks