Hot answers tagged

4

In general your answers were valid. But to create a better impression you could communicate the points which show you have deeper understanding of APIs and API testing. You can mention about web services, APIs REST, SOAP, WSDL, XML, JSON, different methods (POST, GET, DELETE) etc so they get the perception that you have technical understanding of these ...


3

The answer is similar to real world examples, both Motor Cycle (2 wheeler) and Car (4 wheeler) provides approximately same speed and can carry a person from one place to another, so why two (or in actuality more than two) types of vehicles are there and that too with further classifications (different brand designing different vehicles) i.e. because each ...


3

What questions should I ask the developers so that i can proceed with automating? It depends what kind of test you want to have, if it is only end2end testing then "Base URI" should be enough for you. If you need to test more than that (e.g Tests which need mocking), you may need to have access to the project code to add your test code there. For ...


3

We use Postman for considerable basic testing during the early stages of development. We then have used Gatling (http://gatling.io/#/) to facilitate load, regression, and stress testing.


3

From your question I'm gauging that we're talking about web service APIs (i.e. REST, SOAP, etc.) and not code-level functional APIs (i.e. Java APIs, etc.). So, a followup question for you is what role are you interviewing for? QA tester, API engineer, DevOps? Are the APIs you're tasked with testing ones that the company is building/managing in house, or are ...


3

Well, an API is such a loaded term. It can be REST, SOAP, RMI, or native C++ library API, etc., so the tooling will depend on that. Particular test scenarios will depend on that as well. For instance, for REST or SOAP over HTTP you may want to check popular HTTP-related attacks like HTTP Response Splitting, etc. You may also check if API is well-defined, ...


2

Using this tip/trick you can modify the response's header. The example shows modifying the content but you should be able to get the gist. if( request.response == null ) return // get response content def content = context.httpResponse.responseContent // manipulate content content = content.replaceAll( "555", "444" ) // write it back ...


1

I have working in a not dissimilar industry and had the following setup; TrainTestSuite (this might be per supplier/operator) -testcase->SingleBooking -testcase->ReturnBooking Both would utilize the same endpoint as the Test Suite Within each test case I would have the following; Properties (containing from and to locations) PropertyTransfer ...


1

Couple of options Duplicate the suite, one with one path, one with the other. This could cause you maintenance headaches though Create a variable for the property (template) and have a conditional go to in a test script Groovy Script (If env = UAT go to Properties (UAT)) Properties (Live endpoint) Property Transfer to endpoint of Test Steps Test steps ...


1

A lot of devs I know use PostMan, a Chrome app. I have written my own tool using .Net that allows me to use pre-formatted requests with a given type reflected from a .dll file. A REST client is like a browser. It makes a request and does something with the response (like printing out the JSON response).


1

Regexp is your friend matches(//ns:XPathToIt/ns:password,'\w{7,}') The \w{7,} will match a string with 7 characters. In the Expected Result put "true". SoapUI Assertions


1

So basically I found out the way to do it through a Groovy Script. I used the JsonSlurper util as with Groovy is really flexible and allows me to manage the XML Response as a Key-Value data structure. An example of my solution is shown below: import groovy.json.JsonSlurper def xPath = '//ADDITIONAL_INFORMATION' def addinfo = context.expand( ...


1

You can check this great blog: http://www.softwaretestinghelp.com/web-services-api-testing-tool-soapui-tutorial-1/ Second you can check the free courses here: http://soapui-tutorial.com/


1

I am afraid you can'd do it via the GUI. However, you can set property files for another case via a groovy script with something like tCase = prj.testSuites['TestSuiteName'].testCases['TestCaseName'] tCase.setPropertyValue( "MyProp", someValue ) For some reason you cant perform it as a single line in my expirience. ...


1

Runscope provides a Web UI for creating tests. There is no code to write for standard assertions. You can write more complex assertions using Javascript. It is a cloud based service, which allows tests to be run from data centers around the world, which is useful when testing response times. You can also use our local agent to test APIs that are behind ...


1

For simple user-friendly tool to test REST API, POSTMan is a great tool. It is easy to use. And, best for smoke testing. You can create request quickly. However, since you have some experience in automated testing. I would recommend to have automated test using JUnit. Basically, you need three thing to create automated test: Create Http Client. Expected ...


1

It seems Countries WSDL path is wrong. You can try TempConvert Wsdl as an example in W3Schools Web site: http://www.w3schools.com/webservices/tempconvert.asmx?wsdl When you load the wsdl from SoapUI tool you will see 2 operations belongs to this web service: CelciusToFahrenheit FahrenheitToCelsius


1

Part of the issue with RESTful Web APIs is there really isn't a standard as of yet. If there is a WADL for the Web API than SoapUI will typically work well. If not, than you're going to spend as much time, if not more, using SoapUI to work with your system than you would with any of the slew of tools that either exist or can be custom created. I am ...



Only top voted, non community-wiki answers of a minimum length are eligible