User Profile

chimas

Occasional Contributor

Joined 10 years ago

7 Posts1 Solution

View All Badges

User Widgets

Contributions

REST response from local cache
Hi, I'm facing an odd situation while using ReadyAPI but it's not a problem with SOAPUI . I have one test case with 4 REST steps: First step is one GET to method get Language. To see what is the current language. Second step change to another language. Third step is the same as First step. To see if the language was changed. Fourth step return the language to the original state. This sequence works very well if you run it on SOAPUI but with ReadyAPI the Third step is always returning the same value from the First step. I'm I have confirmed that this request is not reaching my WS. Is there any configuration inside Ready API to disable "local cache". I'm using Ready API 1.5.0 and SOAPUI 5.3.0 Thank you, Rodrigo Petry
Solved
8 years ago Place ReadyAPI Questions
1.9KViews
0likes
1Comment
Re: Settings.xml file for a composite project very large is that normal?
Thank you Tanya I found inside settings.xml file this xml tag "<con:soapui-project" 1249 times. And I delete all these "old" projects inside settings.xml and now the file has only 33KB and everything is working fine. As this is a shared project I'll ask everybody that is using this project to install this latest version of Ready API. Thank you for your answer. Rodrigo Petry
9 years ago Place ReadyAPI Questions
2.1KViews
0likes
0Comments
Settings.xml file for a composite project very large is that normal?
Hi, I have a composite project and the Settings.xml file has 34MB. Ready API is failing to save the project before close the project. I didn't research much inside this file but probably it's duplicating the project content inside this file. For example one string that I have only inside the Project TearDown Script I can found it 312 times inside this settings.xml file. Something is wrong here :) Is there any way to "refresh" this settings.xml file with the actual project configuration? Or should I change one configuration inside ReadyAPI to avoid this problem? Thanks, Rodrigo Petry
Solved
9 years ago Place ReadyAPI Questions
2.1KViews
0likes
2Comments
Re: From Project teardown script can I access the status, timetaken of TestSuite and TestCase?
Thank you Samy I think this option of Junit style report can solve my problem. But do you know if I can call the generation of this Junit report inside Project Teardown script? So in that way I can open this file inside the Teardown and add it to the body of the email, not as attachment. For my original question I found a solution saving one file with html code on the project path and incrementing the results on each TestSuite - TearDown end on the Project - TearDown I'm opening that file and populating the body of the email with the content of this file.
10 years ago Place ReadyAPI Questions
1.9KViews
0likes
1Comment
From Project teardown script can I access the status, timetaken of TestSuite and TestCase?
I'm trying to access from a Project teardown the result of the test execution. Inside this project I have 2 Test Suites. One with 2 testCases and one with 1 testCase The goal is to build an email with the Project result inside the body (nothing attached) NAME DETAILS RESULT PROJECT FAIL -TestSuite 1 Response time = 3904 ms PASS --TestCase 1 Response time = 1589 ms PASS --TestCase 1.1 Response time = 2315 ms PASS -TestSuite 2 Response time = 717 ms FAIL --TestCase 2 Response time = 717 ms FAIL I tried runner, context but without success. Can someone help me with it? Thanks, Rodrigo Petry
10 years ago Place ReadyAPI Questions
1.9KViews
0likes
3Comments
ReadyAPI 1.4.1 Inline Command is always executed
Hi In Soapui I used to use this approach to create random user names. But it is not working as expected inside READY API. Inside a SOAP request I have something like this: <userName>User_${=(int)(Math.random()*1000)+9999}</userName> That will generate one random name every time this request is called. Example: <userName>User_5555</userName> This is fine but when I'm trying to read this generated name from another Step on the same test case one new number will be generated. I'm using this command to read this user name from the RawRequest: ${setNewUser#RawRequest#//userName} And that random command will be executed again, generating a new user name every time I try to read the username generated on that other Test Step. Unfortunately it was working on SOAPUI 5.2.0 but it is not working on READY API WorkAround: I don’t want to change all projects I have but I know it’s possible to use this workaround to avoid this Issue. Write an Groovy script to generate this random name and storing it on a TestCase custom property.
Solved
10 years ago Place ReadyAPI Questions
4.2KViews
0likes
6Comments
I'm in SoapUI NG how to set HTTP Headers for all requests inside Test Suite?
I have some projects with some TestSuites and tons of WS requests. Now I have one new HTTP Header to add to all Requests. This header will be the same to all Request. Is there any way to add this new header to all requests inside the Project or Test Suite? Thanks, Rodrigo Petry
10 years ago Place ReadyAPI Questions
1.2KViews
0likes
1Comment