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

## Thinking why before how
As we learn more and more about testing, our questions start to change slightly. We become more interested in knowing the value-add to the end user’s life than the exact tasks. In other words, we begin to think about the why behind each new feature, not the how.

When we're working in a team, we're probably going to be handed a list of tasks to execute. Since those tasks were written by someone else, they have already thought about the why for us.

If that's the case, we need to be a part of that process. We need to understand the solution from beginning to end.

# Thinking why before how
As we learn more and more about testing, our questions start to change slightly. We become more interested in knowing the value-add to the end user’s life than the exact tasks. In other words, we begin to think about the why behind each new feature, not the how.

When we're working in a team, we're probably going to be handed a list of tasks to execute. Since those tasks were written by someone else, they have already thought about the why for us.

If that's the case, we need to be a part of that process. We need to understand the solution from beginning to end.

Let’s learn the importance of communicating behavior to write effective tests.


Before We Start

The Why Behind Testing

The How Behind Testing

Planning

The Feature Layer

The Request Layer

The Unit Layer

Conclusion

Communicating Behavior

Thinking why before how