Useful API Documentation
SmartBear is presumably working diligently at adding comments to their nearly-comment-free, Javadoc-generated API documentation (https://www.soapui.org/apidocs/overview-summary.html). I'm wondering h...
Forum Discussion
After going thru the links and soapui's API, understand that Description is empty for some. Is that what you wanted to convey?
Package descriptions are empty excessively often. Class descriptions are empty excessively often. Method descriptions are empty excessively often. Field descriptions are empty excessively often. Basically, where there should be human-written words conveying the intended meaning/use/functionality/etc. behind an item (package, class, method, field, etc?), there is almost always no such words.
Compare the level of detail provided by SmartBear for one of SoapUI's core classes:
https://www.soapui.org/apidocs/com/eviware/soapui/impl/wsdl/testcase/WsdlTestCase.html
with the detail provided for this core class from MongoDB API:
https://api.mongodb.com/java/current/com/mongodb/DBCursor.html
The difference is incredible. On top of being super helpful, the detailed, thoughtful commentary in the MongoDB API documentation generates the feeling that the developers and maintainers of MongoDB care about their users. I get quite the opposite feeling when it comes to SoapUI. That is what I want to convey. More or less.
- Understand the point. But, that is current not in control.
May be the best thing now could be to look into the problem that is being faced. If you have any specific issue while scripting something, then posting that one would help to resolve the problem, and I believe that would appropriate at the moment.
