Using Artifice to Stub Server Responses

Submitted by Christoph Olszowka 2011-01-05 07:11:40 UTC
Source:  http://thelucid.com/2011/01/04/using-artifice-to-stub-server-responses/

Referenced projects

Artifice

Replaces Net::HTTP with a subclass that routes all requests to a Rack application

Rubygem artifice

Total Downloads
113834
Releases
2
Current Version
0.6
Released
2010-10-25 02:00:00 UTC
First Release
2010-03-24 07:00:00 UTC

Github wycats/artifice

Watchers
214
Forks
16
Development activity
Inactive
Last commit
2013-01-25 23:24:14 UTC
Top contributors
Contributors
5
Issues

Rack

Rack provides a minimal, modular and adaptable interface for developing web applications in Ruby. By wrapping HTTP requests and responses in the simplest way possible, it unifies and distills the API for web servers, web frameworks, and software in between (the so-called middleware) into a single method call. Also see http://rack.github.io/.

Rubygem rack

Total Downloads
68858686
Releases
61
Current Version
1.4.6
Released
2015-06-16 00:00:00 UTC
First Release
2007-03-02 23:00:00 UTC
Depends on following gems
Depending Gems
2116

Github rack/rack

Watchers
2353
Forks
924
Development activity
Active
Last commit
2015-06-24 19:14:05 UTC

Fakeweb

FakeWeb is a helper for faking web requests in Ruby. It works at a global level, without modifying code or writing extensive stubs.

Rubygem fakeweb

Total Downloads
1636832
Releases
14
Current Version
1.3.0
Released
2010-08-22 07:00:00 UTC
First Release
2009-03-11 07:00:00 UTC
Depends on following gems
Depending Gems
1073

Github chrisk/fakeweb

Watchers
915
Forks
103
Development activity
Inactive
Last commit
2013-12-03 01:53:02 UTC
Contributors
19
Issues

Webmock

WebMock allows stubbing HTTP requests and setting expectations on HTTP requests.

Rubygem webmock

Total Downloads
5913742
Releases
79
Current Version
1.21.0
Released
2015-03-28 00:00:00 UTC
First Release
2009-11-20 00:00:00 UTC

Github bblimke/webmock

Watchers
1411
Forks
206
Development activity
Less active
Last commit
2014-06-22 11:34:05 UTC
×

In order to continue, you must be signed in using your Github account.

If you're signing in using this account for the first time Github will ask for your permission to give access to your public user data to the Ruby Toolbox.

Although the Github Authorization page does not mention it, the request includes read-only access to your verified email address (user:email OAuth scope). This is neccessary so there's a way to notify you about comments, information about your accepted project edits and the like. You can review your notification settings on your account page once you're signed in.