Add controller tests for resource-permissions failures

❮ Back Next ❯

Tasks

• Add non-happy-path controller tests to check that the edit, update and destroy actions behave correctly when the limerick to be modified does not belong to the signed-in user.

Steps for each controller test

• Add test:
  • test/controllers/limericks_controller_test.rb - controller test file.
  • Copy the corresponding happy-path test.
  • Rename the copy to reflect the new expectations:
    • "should not get edit if lack permissions" - name of new edit test.
    • "should not update limerick if lack permissions" - name of new update test.
    • "should not destroy limerick if lack permissions" - name of new destroy test.
• Arrange:
  • Retrieve User fixture object one.
  • Retrieve User fixture object two.
  • Retrieve one of user one’s limericks (the first one in their collection).
  • Sign in user two.
• Act:
  • No change needed.
• Assert:
  • assert_no_difference - check that the number of Limerick objects in the database has not changed.
  • assert_response - check that the HTTP response has a redirect status code.
  • assert_redirected_to - check that the HTTP redirect was to the root URL.
  • assert_not_nil - check that a flash['error'] message was set.
• Run tests and inspect coverage report:
  • rails test -v - command to run tests and generate coverage report.
  • coverage/index.html - coverage report to view in web browser.

Reference Code

---

❮ Back Next ❯