srinubalsu
Senior Member
Joined 10 years ago
User Profile
User Widgets
Contributions
BUG: ReadyAPI is not calculating OAuth1.0 signature correctly if I use Content-Type as FORM
ReadyAPI is not calculating OAuth1.0 signature correctly if I use Content-Type as application/x-www-form-urlencoded (FORM data). It calculates and works fine if I use the Content-Type as application/json I don't know what is the difference if anyone has seen this before. is there any workaround for the issue.830Views0likes1CommentENH: Repeat the HTTP/REST request for n times with specified delay between each trials until passed
Requesting for an enhancement to repeat the every HTTP/REST request for n times with specified delay between each trials until it passes its assertions. We are facing a problem in our testing while using two web interfaces. The first REST send a request to second HTTP/REST service which will take some time (Not sure, it may be from 60secs to 300secs anywhere). With a hard coded delay, it was very tough and wasting lot of time for testing. With this feature, it saves lot of time and effort. I knew this can be done through conditional step, but it has so much work involved with each step. BTW, basic behavior of any HTT/REST request should not change by default. it should behave like as usual now. One more this is, it is test step level feature.5.7KViews8likes2Comments