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

## The what
One of the most confusing parts of testing is knowing what to test. We will talk about the how in a minute, but if you have already spoken to your stakeholder, you should know what you need to test.



We already have our tests written. That's where we start.

## The _what_
If we don't know what to test, we don't yet understand the application's behavior. We do not have the whole picture. But if we spend the time up front to talk about it, we will have everything we need to get started.

We start with multiple user stories that describe the future behavior of our application. They tell us how the application will behave when it is finished. And those user stories are our *what*.

## The _how_
Now let's talk about the *how*.

The struggle with the how consists of a few things.

First is the Domain Specific Language (DSL) that every testing framework uses to write tests. But that's the easy part. It's just like learning to use new methods in Ruby. It takes some time in the beginning and maybe a few thousand lookups in the docs, but once we're familiar with the framework's syntax, there's not much else to it.

It is not a big problem, even if it initially feels like it.

> **Note:** The real problem is knowing where to put the tests and what kind of test we should write for the different features we want to test. So that deserves a little more detail.


# The what
One of the most confusing parts of testing is knowing what to test. We will talk about the how in a minute, but if you have already spoken to your stakeholder, you should know what you need to test.



We already have our tests written. That's where we start.

# The _what_
If we don't know what to test, we don't yet understand the application's behavior. We do not have the whole picture. But if we spend the time up front to talk about it, we will have everything we need to get started.

We start with multiple user stories that describe the future behavior of our application. They tell us how the application will behave when it is finished. And those user stories are our *what*.

# The _how_
Now let's talk about the *how*.

The struggle with the how consists of a few things.

First is the Domain Specific Language (DSL) that every testing framework uses to write tests. But that's the easy part. It's just like learning to use new methods in Ruby. It takes some time in the beginning and maybe a few thousand lookups in the docs, but once we're familiar with the framework's syntax, there's not much else to it.

It is not a big problem, even if it initially feels like it.

> **Note:** The real problem is knowing where to put the tests and what kind of test we should write for the different features we want to test. So that deserves a little more detail.


Let’s learn how to determine the what for testing.


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

Knowing What to Test

The what

The