Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Rspec Essentials
  • Table Of Contents Toc
  • Feedback & Rating feedback
Rspec Essentials

Rspec Essentials

By : Tadayon
3.3 (3)
close
close
Rspec Essentials

Rspec Essentials

3.3 (3)
By: Tadayon

Overview of this book

This book will teach you how to use RSpec to write high-value tests for real-world code. We start with the key concepts of the unit and testability, followed by hands-on exploration of key features. From the beginning, we learn how to integrate tests into the overall development process to help create high-quality code, avoiding the dangers of testing for its own sake. We build up sample applications and their corresponding tests step by step, from simple beginnings to more sophisticated versions that include databases and external web services. We devote three chapters to web applications with rich JavaScript user interfaces, building one from the ground up using behavior-driven development (BDD) and test-driven development (TDD). The code examples are detailed enough to be realistic while simple enough to be easily understood. Testing concepts, development methodologies, and engineering tradeoffs are discussed in detail as they arise. This approach is designed to foster the reader’s ability to make well-informed decisions on their own.
Table of Contents (12 chapters)
close
close
11
Index

Using hooks

When a unit test requires a few setup steps, we can just include those steps in the test case before our assertion. For example, we may want to create some entries in a database or configure a service before we execute a test.

When the setup is more complex, it can clutter the test case, making the intent of the test harder to understand while increasing the effort required to maintain the test code. Even if the setup steps are short, if they are repeated in many places, duplication of code can lead to similar problems.

It is common for a setup to require cleanup or teardown steps to ensure tests don't interfere with each other. For example, if we added a few records to a database in a setup phase, we want to remove those records so that subsequent tests start off with a clean environment. Again, we can simply include the teardown steps in the test case after our assertion. This poses even larger problems than setup, because in addition to the issues of clutter and lower...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Rspec Essentials
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon