Controller Testing Activity

❮ Back Next ❯

---

Controller tests are automated tests to detect bugs in how our app processes and responds to HTTP requests.

Activity Goals

• Learn to write controller tests for index controller actions.
  • Cover happy path cases.
  • Cover actions that that require user authentication with Devise.
• Understand the limitations of automated tests for revealing bugs.

How to Start

We will write and run controller tests for a sample app, LimerIQ, a limerick (poem) authoring and sharing app (https://github.com/human-se/limeriq-f23).

To get started, perform the following steps:

• Clone the example repo:

git clone git@github.com:human-se/limeriq-f23.git testing-activity-app

• cd into the working tree.

• code . to open the project in VS Code.

• bundle install to ensure that the project Ruby gems are installed.

• rails db:migrate:reset and rails db:seed to initialize and add seed data to the database.

• rails s to run the development web server.

• Open http://localhost:3000 in a web browser, and try using the app to get a sense for its features. You can sign in as either of these users:
  • Email: alice@email.com, Password: password
  • Email: bob@email.com, Password: password

• Note that a user must be signed in to create new limericks.

• Note that a user “owns” the limericks they create—they are the only one who can edit or delete their limericks.

• Note that there are two index pages—one that shows all limericks and one that shows only the signed-in user’s limericks.

• Note that, on the index pages, the limericks are displayed using “cards”.

---

❮ Back Next ❯