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

# Add our first test
The first step is to create a new file for our new feature.

The file can be generated using the following command:
```
$ touch features/user_registration.feature
```

We need to add the following text to the newly-generated file:




Feature: User registration
   As a first-time visitor
   I want to be able to create an account
   So that I can access the members area

  Scenario: I create an account
    Given I am on the homepage
    And I click on the registration link
    When I fill in and submit the registration form
    Then I should see a registration confirmation message
    And I should receive a confirmation email

# Run our test
As mentioned previously, the test guides everything we do moving forward. So, the logical next step will be to run the test and see what happens.
 
We’ll use the following command to run the test:

```bash
$ bundle exec cucumber features/user_registration.feature
```
> **Note**: The `bundle exec` can be omitted when running locally, depending on how your application is set up.

Running the test tells us we have one scenario with no step definitions defined yet. It also gives us a nice template to describe what each of those lines in our feature test means.


Before We Start

The Why Behind Testing

The How Behind Testing

Planning

The Feature Layer

The Request Layer

The Unit Layer

Create a Bill Split Application Using Ruby on Rails

Conclusion

Our First Test: Get Homepage

Add our first test

Run our test