set up branch

Author: akanshmurthy

sites/en/docs/docs.step

@@ -24,6 +24,10 @@ site_desc 'message-board', <<-MARKDOWN
 Build a message board! This curriculum is for students who have completed the Suggestotron and the Job Board curricula. This curriculum is a challenge because it won't tell you what to type in!
 MARKDOWN
 
+site_desc 'testing', <<-MARKDOWN
+Increase the stability of your Rails app by learning about tests: what they are, why they're used, and how to use them! This curriculum is for students who have completed the Suggestotron and the Job Board curricula. This curriculum is open to everyone but there is a challenge at the end!
+MARKDOWN
+
 h1 'Frontend'
 
 site_desc 'frontend', <<-MARKDOWN

sites/en/testing/advanced_concepts.step

@@ -0,0 +1,5 @@
+message <<-MARKDOWN
+  Advanced concepts.
+
+  Bla bla bla.
+MARKDOWN

sites/en/testing/testing.step

@@ -0,0 +1,28 @@
+message <<-MARKDOWN
+  Bla bla bla.
+
+  Bla bla bla.
+MARKDOWN
+
+tip "This is not a self-paced curriculum. You should use the discussion sections on each page to make sure everyone is together!"
+
+message <<-MARKDOWN
+  # Notable Things
+
+  As you might have noticed, we're assuming you've already been to a RailsBridge workshop before or have otherwise already explored a Rails app, and are ready for deeper knowledge.
+
+  We're also going to skip deploying to Heroku this time around, but you can definitely use the instructions from the Suggestotron curriculum to deploy your app to the internet!
+MARKDOWN
+
+important "This curriculum is written for Rails 5. Things will get awkward / broken if you're using an earlier version of Rails, so if you skipped the Installfest, you need to upgrade to Rails 5 now."
+
+message <<-MARKDOWN
+  # Tips for everyone:
+
+  * When adding code, it's awesome for students to walk through the code line by line and say out loud what is happening. (i.e., "The string is being stored in the instance variable" or "The method `snorgle` is being defined"). If you do it every time, you'll get really comfortable with the vocabulary of Rails!
+  * Error messages are your friend! Read them carefully, and practice understanding what Rails is telling you. Seeing an error and just diving back into your code is a natural reaction, but stop! Then read, think, and talk about what the error means before fixing it.
+MARKDOWN
+
+insert '../intro-to-rails/working_effectively_and_efficiently'
+
+next_step "what_are_tests"

sites/en/testing/testing_frameworks.step

@@ -0,0 +1,7 @@
+message <<-MARKDOWN
+  Testing frameworks.
+
+  Bla bla bla.
+MARKDOWN
+
+next_step "advanced_concepts"

sites/en/testing/types_of_tests.step

@@ -0,0 +1,7 @@
+message <<-MARKDOWN
+  Types of tests.
+
+  Bla bla bla.
+MARKDOWN
+
+next_step "testing_frameworks"

sites/en/testing/what_are_tests.step

@@ -0,0 +1,7 @@
+message <<-MARKDOWN
+  What are tests?
+
+  Bla bla bla.
+MARKDOWN
+
+next_step "types_of_tests"