Restful API Resources

A place to discover and rediscover Restful API.

Wednesday, November 21, 2012

Why having an API matters: testing

Why having an API matters: testing:
You know when they tell you exposing an HTTP API for your application (usually a REST-like one) is positive for reuse and accessing it in unforeseen ways? That's whay just happened to me last week while trying to put together some functional tests.

Posted by Techknight at 10:09 AM
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest

No comments:

Post a Comment

Newer Post Older Post Home
Subscribe to: Post Comments (Atom)

Blog Archive

  • ►  2018 (1)
    • ►  November (1)
  • ►  2017 (2)
    • ►  August (1)
    • ►  June (1)
  • ►  2015 (8)
    • ►  November (2)
    • ►  September (4)
    • ►  July (1)
    • ►  June (1)
  • ►  2014 (9)
    • ►  December (1)
    • ►  September (3)
    • ►  August (4)
    • ►  July (1)
  • ►  2013 (25)
    • ►  September (1)
    • ►  July (1)
    • ►  April (6)
    • ►  March (1)
    • ►  February (6)
    • ►  January (10)
  • ▼  2012 (47)
    • ▼  November (8)
      • Why having an API matters: testing
      • When REST isn't good enough
      • Spring HATEOAS - Library to support implementing r...
      • Cross domain REST calls using CORS
      • All webservices should be RESTful - why aren't they?
      • Spock and testing RESTful API services
      • Performance Analysis of REST/HTTP Services with JM...
      • How To Perform REST Calls From Java
    • ►  October (4)
    • ►  September (10)
    • ►  August (2)
    • ►  July (23)
Simple theme. Powered by Blogger.