Updates mod 2 feature testing lesson circa 2103

module2/lessons/archive/feature_testing_legacy.md

@@ -0,0 +1,240 @@
+---
+title: Feature Testing with RSpec
+layout: page
+---
+
+## Warm Up
+
+* In SetList, what does a User do to visit the Songs index?
+    * What actions do they take?
+    * What do they click on?
+    * What do they type?
+* What does a user expect when visiting the Songs index?
+
+## Setup
+
+This lesson builds off of the [ActiveRecord Associations Lesson](./active_record_associations). You can find the completed code from this lesson on the `ar_associations` branch of [this repo](https://github.com/turingschool-examples/set_list/tree/ar_associations)
+
+## Gems
+
+Add the following Gems to your Gemfile. Since these are all testing/debugging tools, we will add them inside the existing `group :development, :test` block:
+
+  - `rspec-rails` = our test suite
+  - `capybara` = gives us tools for feature testing
+  - `launchy` = allows us to save_and_open_page to see a live version on the browser
+  - `simplecov` = track test coverage
+
+Your Gemfile should now have:
+
+```ruby
+group :development, :test do
+  gem 'rspec-rails'
+  gem 'capybara'
+  gem 'launchy'
+  gem 'simplecov'
+  gem 'pry'
+end
+```
+
+Always run `bundle install` whenever you update your Gemfile.
+
+## Install and set up RSpec
+
+```bash
+$ rails g rspec:install
+```
+
+What new files did this generate?
+
+- `./.rspec` file
+- a whole `./spec/` directory
+- `./spec/rails_helper.rb` is the new `spec_helper`, holds Rails-specific configurations
+- `./spec/spec_helper.rb` - where we keep all specs that don't depend on rails
+
+## Configure SimpleCov
+
+At the top of your `rails_helper.rb`, add these lines:
+
+```ruby
+require 'simplecov'
+SimpleCov.start
+```
+
+# Feature Testing
+
+## What are Feature Tests?
+
+* Feature tests mimic the behavior of the user: In the case of web apps, this behavior will be clicking, filling in forms, visiting new pages, etc.
+* Just like a user, the feature test should not need to know about underlying code
+* Based on user stories
+
+## What are User Stories?
+
+* A tool used to communicate user needs to software developers.
+* They are used in Agile Development, and it was first introduced in 1998 by proponents of Extreme Programming.
+* They describe what a user needs to do in order to fulfill a function.
+* They are part of our "top-down" design.
+
+```txt
+As a user
+When I visit the home page
+And I click on the link New Task
+Then I see a form to create a task
+
+And I fill in title
+And I fill in description
+And I click submit
+Then my task is saved
+```
+
+We can generalize this pattern as follows:
+
+```
+As a [user/user-type]
+When I [action]
+And I [action]
+And I [action]
+...
+Then [expected result]
+```
+
+Depending on how encompassing a user story is, you may want to break a single user story into multiple, smaller user stories.
+
+## Capybara: Feature Testing Tools
+
+[Capybara](https://github.com/teamcapybara/capybara#using-capybara-with-rspec)
+
+Capybara is a Ruby test framework that allows you to feature test any RACK-based app.
+
+It provides a DSL (domain specific language) to help you query and interact with the DOM.
+
+For example, the following methods are included in the Capybara DSL:
+
+* `visit '/path'`
+* `expect(current_path).to eq('/')`
+* `expect(page).to have_content("Content")`
+* `within ".css-class"  { Assertions here }`
+* `within "#css-id"  { Assertions here }`
+* `fill_in "identifier", with: "Content"`
+* `expect(page).to have_link("Click here")`
+* `click_link "Click Here"`
+* `expect(page).to have_button("Submit")`
+* `click_button "Submit"`
+* `click_on "identifier"`
+
+## Always, Always, Always, Write Tests First
+
+As usual, we are going to TDD our applications. There are two approaches we could take here:
+
+1. Bottom Up: Start with the smallest thing you can build and work your way up. In the context of a web app, this means you start at the database level (model tests).
+1. Top Down: Start at the end goal and work your way down. In the context of a web app, this means you start by thinking about how a user interacts with the application (feature tests).
+
+Both are valid approaches. We are going to work Top Down.
+
+## Testing the Songs Index
+
+Thinking back to the warmup, let's write a user story for our Songs index:
+
+```text
+As a user,
+when I visit '/songs'
+I see each song's title and play count
+```
+
+First, let's make a directory for our feature tests:
+
+```bash
+$ mkdir spec/features
+```
+
+And a directory for all features related to `songs`:
+
+```bash
+$ mkdir spec/features/songs
+```
+
+Finally, create your test file:
+
+```bash
+$ touch spec/features/songs/index_spec.rb
+```
+
+The names of the files you create for feature testing MUST end in `_spec.rb`. Without that 'spec' part of the filename, RSpec will completely ignore the file.
+
+How many tests should go in one file? It's totally up to you, but having multiple tests in a file is marginally faster than putting a single test in a single file. Also, grouping lots of tests into one file allows you to share the setup across your tests.
+
+You can group your test files into subfolders to organize them in a similar format to your `/app/views` folder, and can help with strong organization. Every team you work on, every job you have, could have a completely different organizational method for test files, so keep that 'growth mindset' and be flexible!
+
+```
+/spec
+/spec/features
+/spec/features/songs
+/spec/features/songs/index_spec.rb
+/spec/features/songs/user_can_see_all_songs_spec.rb
+/spec/features/songs/user_can_see_one_song_spec.rb
+etc
+```
+
+Inside our `index_spec.rb `:
+
+```ruby
+require 'rails_helper'
+
+RSpec.describe "songs index page", type: :feature do
+  it "can see all songs titles and play count" do
+    song_1 = Song.create(title:       "I Really Like You",
+                         length:      208,
+                         play_count:  243810867)
+    song_2 = Song.create(title:       "Call Me Maybe",
+                         length:      199,
+                         play_count:  1214722172)
+
+    visit "/songs"
+
+    expect(page).to have_content(song_1.title)
+    expect(page).to have_content("Play Count: #{song_1.play_count}")
+    expect(page).to have_content(song_2.title)
+    expect(page).to have_content("Play Count: #{song_2.play_count}")
+  end
+end
+```
+
+## Practice
+
+Write a test for the following user stories. Then, use TDD to implement the feature.
+
+```
+Practice User Story 1
+
+As a user
+When I visit a Song show page
+Then I see the song's title, length, and play count
+```
+
+```
+Practice User Story 2
+
+As a user
+When I visit a Song show page
+I see a link back to the songs index page
+When I click this link
+Then I am taken to the songs index
+```
+
+```
+Practice User Story 3
+
+As a user
+When I visit an Artist's show page
+Then I see the Artist's name
+And I see the Artist's average song lenth
+And I see the Artist's total song count
+```
+
+
+
+## Checks for Understanding
+
+- What is a Feature Test?
+- What is Capybara?
+- What are User Stories?

module2/lessons/feature_testing.md

@@ -13,16 +13,14 @@ layout: page
 
 ## Setup
 
-This lesson builds off of the [ActiveRecord Associations Lesson](./active_record_associations). You can find the completed code from this lesson on the `ar_associations` branch of [this repo](https://github.com/turingschool-examples/set_list/tree/ar_associations)
+Clone down [this repo](https://github.com/turingschool-examples/set_list_tutorial) and check out the `feature_testing` branch.
 
 ## Gems
 
 Add the following Gems to your Gemfile. Since these are all testing/debugging tools, we will add them inside the existing `group :development, :test` block:
 
-  - `rspec-rails` = our test suite
   - `capybara` = gives us tools for feature testing
   - `launchy` = allows us to save_and_open_page to see a live version on the browser
-  - `simplecov` = track test coverage
 
 Your Gemfile should now have:
 
@@ -38,28 +36,6 @@ end
 
 Always run `bundle install` whenever you update your Gemfile.
 
-## Install and set up RSpec
-
-```bash
-$ rails g rspec:install
-```
-
-What new files did this generate?
-
-- `./.rspec` file
-- a whole `./spec/` directory
-- `./spec/rails_helper.rb` is the new `spec_helper`, holds Rails-specific configurations
-- `./spec/spec_helper.rb` - where we keep all specs that don't depend on rails
-
-## Configure SimpleCov
-
-At the top of your `rails_helper.rb`, add these lines:
-
-```ruby
-require 'simplecov'
-SimpleCov.start
-```
-
 # Feature Testing
 
 ## What are Feature Tests?