The Artima Developer Community
Sponsored Link

Java Buzz Forum
Mocking an API should be somebody else's problem

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Mike Kaufman

Posts: 125
Nickname: mkaufman
Registered: Jan, 2007

Mike Kaufman started programming in 1973 and is still here.
Mocking an API should be somebody else's problem Posted: Mar 11, 2008 1:19 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by Mike Kaufman.
Original Post: Mocking an API should be somebody else's problem
Feed Title: Closing Braces
Feed URL: https://closingbraces.net/feed/
Feed Description: After-hours notes and opinions on Java and system development.
Latest Java Buzz Posts
Latest Java Buzz Posts by Mike Kaufman
Latest Posts From Closing Braces

Advertisement
In a recent interview, Hani Suleiman expressed the view that mocking/stubbing Java EE constructs can be a bad idea. Whilst I fully agree with that in the context of individual projects, I think the situation is rather different if you can obtain a high-quality, ready-made set of API-specific test-doubles from somebody else - and that it makes sense for such test-doubles to be centrally developed for major APIs.

Read: Mocking an API should be somebody else's problem

Topic: Running Selenium Headless Previous Topic   Next Topic Topic: PHP Security through Suhosin or Hardening Patch

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use