rlong98
Contributor
Joined 12 years ago
User Profile
User Widgets
Contributions
Re: Getting full wsdl from a SoapUI project
🤣😂 They somehow think it's job security lol Now make sure you have access to the database. When you have that it makes a Master test suite. Use the jdbc testStep. Depending on what type of DB they use, you might need other jar files Soap UI to work15KViews0likes0CommentsRe: Automating Tests with Commuinity Version
Welcome to the club. You’re where i am. It takes a lot of reverse engineering to learn code when it’s not your trade. As you learn in soapui it is and can be very messy very messy with all these steps and transfers. if you’re using groovy step as a simple title - don’t waste your time. Name the testStep and use description inside the testStep if you need to explain. But rarely do you. and if you don’t need to use property transfer - don’t unless you need to see what data was collected in a single source. Use the context path to feed the request (get data) The value is in the response. But I’m ocd and still use properties. i also use the testCase property instead of the testStep property - another way of cleansing up the testCase. Or for cross testCase where you need values you can use the testSuite property. no one will shoot you lol - we are all learning2.4KViews0likes3CommentsRe: Getting full wsdl from a SoapUI project
Check the WSDL itself - it should show you the WSDL URL. Usually the Endpoint is the WSDL... it's not simply just a file, but more of a URL. Usually around line 2 or 3 in the wsdl. <xsd:schema targetNamespace="https://graphical.weather.gov/xml/DWMLgen/wsdl/ndfdXML.wsdl"> IF it doesn't have .wsdl just add it and put it in Chrome (as long as you're on your work network/VPN). Scondly - I find is very rude or bad practice that "Whomever" gave the project to you doesn't show you where or how to get the WSDL. Plus it's better to have the WSDL URL so you can update definitions and/or refactor. So - You can do yourself a favor and play the "good charm" and simply ask "I'm looking for the WSDL URL so that I can update the definitions as development continues. Stick to that. Because if you start testing form an old testStep. I wouldn't get into using wsdl as a file - it's just not the best way to go about it - UNLESS you have to for some odd reason. So if it is in Git/SVN and they update them there - then you need that. Now as for Exporting - where you copying/pasting the WSDL Content from the Tab? OR you sing the actual Export feature? That's the only way I know it would be slightly different - namely only the first line something like <?xml version="1.0" encoding="UTF-8"?> Depending on the where the source code is - Maybe GitHub or SVN - you should have access to that. Plus for a Good QA Role - should have a Repository as well to store the project, so others can use it.15KViews1like3CommentsRe: Automating Tests with Commuinity Version
Pro does make things easier - more bells and whistles But you can still Groovy Automation easily. Problem I noticied when using JSON or REST or JDBC or HTTP - I forget if in the Free Version you don't get much "Right Click > Get Data" options? But if you know the Syntax - (or By getting a free month try of Pro - and learn it from Get Data options)... Between TestSteps - I either would Get whatever value you want (save it to a Propery or use directly in the Tag). Then using IF statements in a groovy script... helps make it more dynamic. Hope I wasn't beeing too basic in my answer2.4KViews0likes0CommentsRe: Am preparing "Code Quality Guidelines" document for Ready API. Need inputs...
Oh - so this is for your team "Users of ReadyAPI" ? I normally write to fit both team & business so that it's simple to lead junior testers as well as speak to Business non-technical. In that case I always find typing like I'm writing in grammar school lol. It really does work out kudos. DYNAMIC CODING - API TESTING Field Population will be dynamic by utilizing "context" expressions that will pull the field value from an external Data Source (i.e. Excel, Oracle...) to test an unlimited amount of test scenarios. This will eliminate manual maintenance of the API testing, allowing the test to run automated on various test scenarios... Here I would put in a picture (see attached) The next phase of your document will be to write up Updating Definitions and/or Refactoring - if the WSDL/WADL changes... :catfrustrated: Which depending on HOW MUCH is changes can the Refactoring work - otherwise you screwed... and sadly the Refactoring for me has worked minimal. 1. Always start off with Updating Definitions. Usually I only have myself or the test lead to do that and store the project in SVN or Git because it can get messy. 2. There are tricks in Notepad++ if Refactoring doesn't work... say if the XPath doesn't match up anymore - you can Find/Replace - - but that's when nothing works from Refactoring. Rob1.8KViews0likes0CommentsRe: Am preparing "Code Quality Guidelines" document for Ready API. Need inputs...
Hi Abi, I'm guessing you're referring to a document to "prove quality" ? Since "Code" is very minimal in ReadyAPI - the Quality is more around the "Quality of the Test Suite Project" - and Directors / Business will look for: Repeat-ability of the test Suite (which we know from our build of an API - it is) The Maintenance of the Suite (How much work will it take to maintain or grow the project) The Dynamic Ability - (Data Source vs. Manual Entry (You will fail in any delivery of a document if there will be any manual entries needed in an API) Running & Reporting: If someone needs to open ReadyAPI and run it, that's sort of ok, but most prefer it run by Command Line, included in a Selenium project w/ reporting. As for Addressing Code - it's "how you go about the above" Groovy Scripting code (where it's kept) Groovy Script step, Setup/Tear Down in a testSuite. How it helps in keeping the project dynmaic - whether it calls a DataSource, or Resets the API's to Ready, Changes any values etc... If you have cool reporting tricks where using ONE API and Looping the API where many intense projects we built will use Groovy to add Elements instead of cloning a testStep. Then reporting the results of each is a Win with Business. Any good reporting is. Not sure if that is what you were looking for... Hope it helps.1.8KViews0likes2CommentsRefactoring not matching up when element changes
This seems to be a problem more that I Have to deal with. Dev keeps changing the Schema structure Below is an example where they added <clientDetails> to make a new element, moving the <clientDetail> element down a level. The problem I have is that I cannot figure out how to connect the <clientDetail> to the new Schema, and SoapUI should know that <clientDetails> is a new parent tag. It won't allow the connection. Anything I'm missing? Rob960Views0likes0Comments
