Challenge: Add controller tests for the edit and update actions

❮ Back Next ❯

Tasks

• Add controller tests to check that the LimericksController#edit and LimericksController#update methods function correctly for the happy path.

Steps for LimericksController#edit

• Add Test:
  • Controller test file: test/controllers/limericks_controller_test.rb
  • Test name: "should get edit"
• Arrange:
  • Retrieve User fixture object one.
  • Sign in the user.
  • Retrieve one of the user’s limericks (the first one in their collection).
• Act:
  • Simulate an HTTP GET request.
  • URL helper for HTTP request: edit_limerick_url (with the retrieved limerick as an argument)
• Assert:
  • Use assert_response to check that the response has a success status code (e.g., 200 OK).
  • Use assert_select to check that the rendered page has an h1 HTML element with the text “Edit Limerick”.

Steps for LimericksController#update

• Add Test:
  • Controller test file: test/controllers/limericks_controller_test.rb
  • Test name: "should update limerick"
• Arrange:
  • Retrieve User fixture object one.
  • Sign in the user.
  • Retrieve one of the user’s limericks (the first one in their collection).
• Act:
  • Simulate an HTTP PATCH request.
  • URL helper for HTTP request: limerick_url (with the retrieved limerick as an argument)
  • Params for HTTP request: (the updated limerick title and text)

limerick: {
  title: 'There was an odd fellow named Gus',
  limerick_text: "There was an odd fellow named Gus,\nWhen traveling he made such a fuss.\nHe was banned from the train,\nNot allowed on a plane,\nAnd now travels only by bus."
}

• Assert:
  • Use assert_no_difference to check that the number of Limerick objects in the database has not changed.
  • Use assert_response to check that the HTTP response has a redirect status code.
  • Use assert_redirected_to to check that the HTTP redirect was to the root URL.
  • Use assert_not_nil to check that a flash['success'] message was set.

Screenshots to Submit

• For the edit and update controller tests submit screenshots that includes:
  • The controller test code in VS Code.
  • The terminal output of rails test -v showing that the controller tests ran and passed.

---

❮ Back Next ❯