Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Rspec Essentials

You're reading from   Rspec Essentials Develop testable, modular, and maintainable Ruby software for the real world using RSpec

Arrow left icon
Product type Paperback
Published in Apr 2016
Publisher
ISBN-13 9781784395902
Length 222 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
 Tadayon Tadayon
Author Profile Icon Tadayon
Tadayon
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

RSpec Essentials
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Exploring Testability from Unit Tests to Behavior-Driven Development 2. Specifying Behavior with Examples and Matchers FREE CHAPTER 3. Taking Control of State with Doubles and Hooks 4. Setting Up and Cleaning Up 5. Simulating External Services 6. Driving a Web Browser with Capybara 7. Building an App from the Outside In with Behavior-Driven Development 8. Tackling the Challenges of End-to-end Testing 9. Configurability 10. Odds and Ends Index

Mock HTTP responses with custom helpers


In the specs for the RedisWeatherQuery module that we worked with in Chapter 4, Setting Up and Cleaning Up, we mocked HTTP responses to prevent actual requests being sent during test runs. The code that accomplished this was simple:

let(:json_response) { '{}' }

before do
  allow(weather_query).to receive(:http).and_return(json_response)
end

For most specs, we actually don't need any mock response data, so an empty Hash is good enough. But this approach has some problems. First, we may want to validate the response we receive from the API to ensure it meets our expectations of how it is formatted. Second, we may have mocks in our specs that do not look like anything that the API returns. Third, we are treating the response imprecisely, ignoring the HTTP status code, assuming the body is valid JSON, and caching all responses regardless of success or failure status.

All these shortcomings will lead to bugs in our real-world code. Also, debugging will...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images
Modal Close icon
Modal Close icon