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

**(True or False)** Feature tests are concerned with testing the things that the user can see, while request tests are concerned with testing the things that the user can’t see.


(True or False) Feature tests are concerned with testing the things that the user can see, while request tests are concerned with testing the things that the user can’t see.

We’re sending the registration request to the wrong route.

We’re passing invalid values for `params`.

We need to wrap `params` inside a hash that has a `user` key.

We need to make a `GET` request instead of a `POST` request for user registration.


Which of these is a reason why the test might fail at **line 3**?

```ruby
it "creates a user in the database" do
    params = { email: "jdoe@email.com", password: "secret1234" }
    post user_registration_path, params: params # line 3
    expect(response).to have_http_status(200)
    expect(User.all.count).to eq(1)
end
```


Which of these is a reason why the test might fail at line 3?
<pre><code class="language-ruby">it &quot;creates a user in the database&quot; do
 params = { email: &quot;jdoe@email.com&quot;, password: &quot;secret1234&quot; }
 post user_registration_path, params: params # line 3
 expect(response).to have_http_status(200)
 expect(User.all.count).to eq(1)
end
</code></pre>

The requested path doesn’t exist, so the HTTP status code response will be 404.

A successful post request is followed by a redirect, so the HTTP code response will be 302.

The values for `params` are invalid, so the HTTP code response won’t be 200.


The test is set up correctly and will pass.

Which of these is a reason why the test might fail at **line 4**?
```ruby
it "creates a user in the database" do
    params = { email: "jdoe@email.com", password: "secret1234" }
    post user_registration_path, params: { user: params } 
    expect(response).to have_http_status(200) # line 4
    expect(User.all.count).to eq(1)
end
```

Which of these is a reason why the test might fail at line 4?
<pre><code class="language-ruby">it &quot;creates a user in the database&quot; do
 params = { email: &quot;jdoe@email.com&quot;, password: &quot;secret1234&quot; }
 post user_registration_path, params: { user: params } 
 expect(response).to have_http_status(200) # line 4
 expect(User.all.count).to eq(1)
end
</code></pre>

The `email` and `password` parameters are invalid.

`"action"=>"create"` should be `"action"=>"new"`

`permitted: false` should be `permitted: true`

We run our test with a breakpoint in the `create` action of the Devise registrations controller and receive the following response after entering `params` in the prompt:
```bash
=> <ActionController::Parameters {"email"=>"jdoe@email.com", "password"=>"secret1234", "controller"=>"users/registrations", "action"=>"create"} permitted: false>
```

Identify the issue in the response.

We run our test with a breakpoint in the <code>create</code> action of the Devise registrations controller and receive the following response after entering <code>params</code> in the prompt:
<pre><code class="language-bash">=&gt; &lt;ActionController::Parameters {&quot;email&quot;=&gt;&quot;jdoe@email.com&quot;, &quot;password&quot;=&gt;&quot;secret1234&quot;, &quot;controller&quot;=&gt;&quot;users/registrations&quot;, &quot;action&quot;=&gt;&quot;create&quot;} permitted: false&gt;
</code></pre>
Identify the issue in the response.

By adding a step to the feature file that ensures the user's age is permitted:
```text
User's age should be permitted
```

By displaying the `age` in the view using `current_user.age`

By making `age` a part of the permitted keys in the `configure_sign_up_params` method of the registrations controller

By wrapping the `age` parameter in a `user` hash to ensure that it’s according to the Devise default settings


Which of the following is the correct way to fix an unpermitted sign-up parameter `age` for our Devise user?


Which of the following is the correct way to fix an unpermitted sign-up parameter <code>age</code> for our Devise user?

Test your understanding of request layer testing.

Before We Start

The Why Behind Testing

The How Behind Testing

Planning

The Feature Layer

The Request Layer

The Unit Layer

Conclusion

Quiz: Request Layer