Monday, December 26, 2016

WebService Testing SoapUI_Postmaster FAQ

My FAQ's
---------
What is a API?

An API or Application Programming Interface is a set of programming instructions for accessing a web-based software application.

In general API's are like below, they have server name, paths.., etc

http://<server name>/v1/export/Publisher/Standard_Publisher_Report?format=csv

There are mainly 4 methods involve in API Testing like GET, POST, Delete, and PUT.
______________________________________________________________________

GET :-
The GET method is used to extract information from the given server using a given URI. While using GET request, it should only extract data and should have no other effect on the data.

POST :-
A POST request is used to create a new entity. It can also be used to send data to the server, 
ex.: Customer information, file upload, etc. using HTML forms.

PUT :-
Create a new entity or update an existing one.

DELETE :-
Removes all current representations of the target resource given by a URI.

*** Top 20 API Testing Interview Questions & Answers
http://career.guru99.com/top-20-questions-on-api-testing/

* API Testing with QTP
http://www.guru99.com/api-testing-with-qtp-hp-uft.html

* Jenkins with maven continuous integration

* Use Git and GitHub to manage and share source code
Git hub we can do anything, we can manage or share source code with any one its
all matter of authorization permissions to any user
yes, SOAP UI with XML or WSDL file, it can be jason.xml file

* Angular JS, we use protractor framework in selenium this is part of security
Angular Js is used for open UI hat is free open software where developers use to build the web ui,a nd the protractor framework is used
to test that Angular Js layer

* Angular JS, we use protractor framework in selenium

* Simple Object Access Protocol (SOAP)

* Experience with Quality Tools (Quality Center, Perfecto Mobile, Jira, Rally…  Etc. )
1. Experience with .NET, XML and JSON web services
Experience with .NET, XML and JSON web services - this is more of restful web services testing, did you test Soap UI

* Interface Testing
http://www.guru99.com/interface-testing.html

Interface Testing actually verifies whether the communication between two different software systems are done correctly.

-----------------

* Interface Testing
http://www.guru99.com/interface-testing.html

Interface Testing actually verifies whether the communication between two different software systems are done correctly.

200
Succesful POST request status code
HTTP Status Codes
Value Description Reference
200 OK        [RFC7231, Section 6.3.1]
201 Created        [RFC7231, Section 6.3.2]
202 Accepted [RFC7231, Section 6.3.3]
203 Non-Authoritative Information [RFC7231, Section 6.3.4]

http://www.restapitutorial.com/httpstatuscodes.html

HTTP Status Codes
This page is created from HTTP status code information found at ietf.org and Wikipedia. Click on the category heading or the status code link to read more.
1xx Informational
-----------------
100 Continue
101 Switching Protocols
102 Processing (WebDAV)

2xx Success
-----------
 200 OK
 201 Created
 202 Accepted
 203 Non-Authoritative Information
 204 No Content
205 Reset Content
206 Partial Content
207 Multi-Status (WebDAV)
208 Already Reported (WebDAV)
226 IM Used

3xx Redirection
---------------
300 Multiple Choices
301 Moved Permanently
302 Found
303 See Other
304 Not Modified
305 Use Proxy
306 (Unused)
307 Temporary Redirect
308 Permanent Redirect (experiemental)

4xx Client Error
----------------
 400 Bad Request
 401 Unauthorized
 402 Payment Required
 403 Forbidden
 404 Not Found
 405 Method Not Allowed
 406 Not Acceptable
 407 Proxy Authentication Required
 408 Request Timeout
 409 Conflict
 410 Gone
411 Length Required
412 Precondition Failed
413 Request Entity Too Large
414 Request-URI Too Long
415 Unsupported Media Type
416 Requested Range Not Satisfiable
417 Expectation Failed
418 I'm a teapot (RFC 2324)
420 Enhance Your Calm (Twitter)
422 Unprocessable Entity (WebDAV)
423 Locked (WebDAV)
424 Failed Dependency (WebDAV)
425 Reserved for WebDAV
426 Upgrade Required
428 Precondition Required
429 Too Many Requests
431 Request Header Fields Too Large
444 No Response (Nginx)
449 Retry With (Microsoft)
450 Blocked by Windows Parental Controls (Microsoft)
451 Unavailable For Legal Reasons
499 Client Closed Request (Nginx)


5xx Server Error
----------------
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
505 HTTP Version Not Supported
506 Variant Also Negotiates (Experimental)
507 Insufficient Storage (WebDAV)
508 Loop Detected (WebDAV)
509 Bandwidth Limit Exceeded (Apache)
510 Not Extended
511 Network Authentication Required
598 Network read timeout error
599 Network connect timeout error
 "Top 10" HTTP Status Code. More REST service-specific information is contained in the entry.

-------------------

No comments:

Post a Comment