How to Integrate SOAPUI in VSTS(Visual Studio Team Services)
Can any one please help me in configuring SOAPUI in VSTS, I am getting error while configuring it. I want to know the parameters we need to define/set while integrating it.
i was trying to do this several weeks ago. i got sidetracked by some other work.
ive got some step by step instructions for VSTS/Git. if youre happy to use VSTS/Git combo i will post them tomorrow. like i say i never finished cos of other work, but i do have some good instructions to do this. before you start i would consider all the directory structures for you projects and supporting test evidence etc. as once you convert your project to composite and add the project into your vsts/git repo you quickly use up the allowed 260 characters in the full path length.
I've attached the instructions
the instructions are just for getting it into a VSTS/Git repo - so don't forget any of the soapui project preamble you need to do (shorten all the foldernames, project names, testsuite names, testcase names, teststep names, convert to composite project etc.) needs to be done BEFORE you start using the instructions.
As I said in my previous post - I hit a character limit (I think its about 265) because I have so many different projects with lots of sequential versions of testdata that were making the full path very long - so make sure you seriously consider this before hand.
If you're paths are too long, when you try and convert to composite, you'll get a warning it doesnt work if you hit the limit.
HOWEVER - adding into a VSTS/Git Repo adds additional chars to the full path length - so make sure you well UNDER the character limit - you don't know what will happen in the future and future project work could add to the path length quite a bit if you don't organise your stuff properly
Thanks for sharing the instructions to create Git repo in vsts to used SOAPUI,but what I have really asked is the steps/methods to integrate SOAPUI in vsts which is not mentioned in the attachment.
Really appreciate your effort though.
aah - sorry - if I understand correctly that I dont have - the instructions make the assumption you ALREADY have a VSTS project setup ready for your SoapUI projects and that you've made all the pre-amble alterations to your SoapUI Project before starting with those instructions.
You need to create a project within VSTS to point to.
I don't know how to do this I'm afraid - the DevOps people where I worked own VSTS so they created my project for me.
HOWEVER - I would suggest there have got to be some instructions published for creating a new project in VSTS. I don't have permissions myself to create a project in our VSTS - so I can't do it myself and provide the actions to do this - but it shouldn't be too difficult.
I'd suggest googling "create a project in VSTS" and go from there. Sorry I couldn't be of more help - but once you have the VSTS project and you've updated your SoapUI Project and converted to 'composite' option (as well as selecting the prettyprint wsdl preference) - the instructions I provided will give you everything else you need.
when you say "take care of the bearer token"...
can you rephrase the question please? unless the place where your repo resides has different topological attributes (i "think" thats the corrwct term..??) so the security settings would be different to enable access to the soapui project, if im understanding the question correctly it shouldnt make any difference. however im guessing at what youre question actually is, so could do with an explanation just to be sure!
What I meant was that do we need to take care of any authentication related stuff as well in SOAPUI testing. In my project they use bearer token as a authentication mechanism which expires every hour. So do we need to take care of those things while integrating SOAPUI in VSTS or providing the project as .xml file in VSTS is enough to complete the build.
Can you please elaborate what are you trying to achieve?