Gain insights into good testing practices in Ruby on Rails. Learn the testing mindset, convert requirements into user stories, and master feature, request, and unit tests for comprehensive coverage.

bullet3.tar.gz

foo-copy

second

challenge1

requests

unit

requestChallenge

featureChallenge

unitChallenge

PassingT1

This course aims to teach you how to write better Rails applications by applying good testing practices. You’ll learn about the reasoning behind testing and the process of applying good testing practices. 

In the first half of the course, you’ll learn about the testing mindset and understand its importance. Next, you’ll learn to turn business requirements into user stories. These user stories will become the basis of the code and tests you’ll write.

Once you understand the reasoning and process, you’ll proceed to write the actual tests. You’ll test what is most important to the end user first. So, the first set of tests you’ll learn to write will be feature tests. Finally, you’ll learn to write request tests and unit tests ensuring end-to-end coverage of our application.

Bulletproof Ruby on Rails Applications

We want to spend the least amount of time getting the most coverage from our tests.



# The feature layer
The user stories we’ve learned about thus far translate perfectly to this particular type of test, the feature test. It’s the outer layer of the testing wheel.

We need to start with this layer. It’s what kicks off the implementation of every new feature. We take a new story from the board and put it into a text file, which becomes our feature test.

The first layer is all about what the user can see and how the application behaves from the end user’s point of view. Most applications are a lot more than that, however.

# The request layer

Some things need to happen behind the scenes so that the user can see what they need to see. For example, sending a request to an API is an action triggered by the user, but the actual result is hidden from the user's interface.

Likewise, saving data to the database is an important action that the application requires, but it’s not part of the user’s interface. To ensure our application behaves correctly, we might want to test that we’ve properly saved some data to the database.



Let’s learn about the three layers of the testing wheel in more depth.


The Layers

Let’s learn about the three layers of the testing wheel in more depth.

Before We Start

The Why Behind Testing

The How Behind Testing

Planning

The Feature Layer

The Request Layer

The Unit Layer

Conclusion

The Testing Layers

The feature layer