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

A story describes the journey a user takes through our application to reach their goal. 

A story is a discussion the developer has with the stakeholder regarding the end product.

A story is the thinking process behind the building of an application.


A story describes the details we consider when performing an action to reach our development goals.


Which of these best describes a story?

To help the development team understand the product better

To form a common understanding of the product for both the development team and the stakeholder

To communicate the business goals with the non-technical savvy


**(Select all that apply.)** What’s the use of story mapping sessions?

(Select all that apply.) What’s the use of story mapping sessions?

It helps define the problem at hand in a clearer way

It helps guide our code design and application architecture

It makes implementing the solution easier

It helps to avoid discussing the problem with non-technical persons in the company

 What’s the point of writing tests before the code implementation?


What’s the point of writing tests before the code implementation?

**(True or False)** A goal can have only one action associated with it in a user storyboard.

(True or False) A goal can have only one action associated with it in a user storyboard.

**(True or False)** We can divide our user stories by the type of actor performing the action.


(True or False) We can divide our user stories by the type of actor performing the action.

Test your understanding of the how behind testing.


Quiz: The How Behind Testing


Test your understanding of the how behind testing.

Before We Start

The Why Behind Testing

The How Behind Testing

Planning

The Feature Layer

The Request Layer

The Unit Layer

Conclusion

Quiz: The How Behind Testing