Forum Discussion
I suggest/hoping that the "Get Data" displays the current TestSuite & TestCase on the Top (first on the dropdown list). Also applicable in "Select Content" in assertions window.
As seen on older version (v. 1.5.0) if I am correct.
- gilugopi9 years agoContributor
Couldn't agree more with axeltoushirou. Get data is probably one of the most frequently used features and more ofthen than not testers are fetching data form different parts of the same test case.
Please make it more easier to get data from current test case. Saves a lot of time and reduces manual errors which working with large projects.
Thanks & Regards,
Gilu Gopi
- gilugopi9 years agoContributor
Features I like most
1. Data Source
2. Data Gen
3. Enviornments
4. Get Data
Wish list of improvements.
Most of them are not really a deal breaker but because of these could save some time/effort on users part.
1. When ready api closes, projects which are currently running won't be saved. At the time of existing ready api, I guess it's more important to save changes than running those steps in back ground.
2. Nice to have a feature to stop all tests currently running in Ready API GUI.
3. Have a way to check out floating licnese from Server via command line on headless linux machines.
4. Let users stop JDBC data sources when system is still waiting for a response from server. At the moment, if user creates an expensive query and sends to DB and it takes 10-15 minuts or more to come back, test can be stopped only after this response is received.
5. I love data generator in DataSource. It makes life a lot easy when you test services which create brand new data and you get to test with different names, addresses etc.
But in Property types like 'Street Address', let users mention the max length of address. Many times what happens to me is when I specify street address, the address generated by Ready API is having a higher length than what the DB column supports in background and throws an error.
That's it for now, will post more as and when I remember.
Thanks & Regards,
Gilu Gopi
- gilugopi9 years agoContributor
I got one more suggestion, this is perhaps the highest on my priority list.
Can you improve the Intellisense ( Intelligent auto suggestion/ code completion functionality ) on all groovy editor windows in Ready API? That goes for Groovy Script test step, Script assertions, Setup Script, Teardown Script, Event Handlers etc.
There are a number of Classes, methods, properties etc. which won’t show up in the Groovy editor automatically. But if user already knows those and write it, codes works just fine. I’ll give you a small subset of examples below.
messageExchange.ResponseContent
request.requestHeaders
com.eviware.soapui.support.XmlHolder
If these all show up automatically, it will be a lot more easier to work with Groovy Scripts . Also it helps new testers to learn faster as these options show up in the editor. Other wise they’ll have to refer to external javadoc or support forums to even find out that these options are available.
Related Content
- 11 months ago
- 3 years ago
- 3 years ago
Recent Discussions
- 2 days ago