Go gaga over Machine Learning

"As a significant departure from the REST API, GraphQL requires some not-so-subtle shifts in the way we think about consuming and altering data."  - Mark,Matt Platform engineers GitHub Issues with REST: REST APIs are designed to interact with one specific end point at a time. For example, you can get a list of all your issues on GitHub, but you can’t get a list of issues and the comments on those issues at the same time. This means you often need to make more than one “request” to the API to get the exact information you need. REST API results are determined by the API developer, and they want to make sure you have everything you could possibly want. This often means you are getting way more information than you intend to use. GraphQL is a  more flexible query structure, which allows you to request information based on connections across traditional data points. Running Your First GraphQL Query Navigate to the GraphQL explorer . Once the page ...

Postman has developed a new mock service to enable teams to simulate a backend server. Front-end developers can simulate each endpoint in a Postman Collection (and corresponding environment) to view the potential responses, without actually spinning up a back end. Simulate a back end with Postman's mock service Throughout the development process, delays on the front end or back end can hold up dependent teams from completing their work efficiently. Some API engineers already use Postman to work on endpoints without relying on a front-end UI to simulate API requests. Now, Postman has developed a new mock service to enable teams to simulate a backend server. Here is also a   good repository that uses postman collections demonstrating a variety of use cases for all REST and Platform Extension APIs :  https://github.com/heremaps/postman-collections  

I have been wanting to use this reporting API ever since I heard of it, finally I got my hands dirty with the version 2.0 and I must say it's pretty impressive - If you use either Java or .Net for testing then this is what you need - Extent Reports This is how a sample html report looks like HTML report I shall not go about rewording how to use it, their documentation is pretty good:  http://relevantcodes.com/Tools/ExtentReports2/ExtentJava.html Quick snapshot: Using Maven to download the dependencies Using JUnit for logging and reporting Using TestNG for logging and reporting If you don't want the logging the easiest way without changing anything is using the TestNG Listener -  http://relevantcodes.com/testng-listener-using-extentreports/ Source: http://relevantcodes.com/extentreports-for-selenium/ Happy Test Reporting :P

General API testing guide is useful for background reading:  http://www.soapui.org/testing-dojo/welcome-to-the-dojo/overview.html SmartBear also has a pdf  http://www2.smartbear.com/rs/smartbear/images/SmartBear-SoapUI-101-eBook.pdf   A useful resource for learning against a dummy REST API to try your SOAPUI testcases on, either to play with on their server or install it yourself and mimic your api.    http://jsonplaceholder.typicode.com/ Source: http://www.softwaretestingclub.com/forum/