Add what are tests and testing frameworks

Author: schaui6

sites/en/testing/testing_frameworks.step

@@ -1,7 +1,97 @@
 message <<-MARKDOWN
-  Testing frameworks.
+# What's a testing framework?
+A Testing framework is an execution environment for automated tests. Think of it as the set of assumptions that reminds you when you veer away from those assumptions. In short Test frameworks helps teams organize their test suites and in turn
+help improve the efficiency of testing. 
+
+# Types of testing frameworks
+There are many testing frameworks that work great.  Mini Test is the default testing framework in Rails 5. However, we will be using the RSpec testing framework instead.   
+
+
+# RSpec
+## How to set up RSpec in Rails
+
+Add rspec-rails to both the :development and :test groups in the Gemfile:
+
+<div class="console"><pre>
+group :development, :test do
+  gem 'rspec-rails', '~> 3.4'
+end</pre>
+</div>
+
+Download and install by running:
+
+<div class="console"><pre>
+bundle install
+</pre>
+</div>
+
+Initialize the spec/ directory (where specs will reside) with:
+
+<div class="console"><pre>
+rails generate rspec:install
+</pre>
+</div>
+
+This adds the following files which are used for configuration:
+
+<div class="console"><pre>
+.rspec
+spec/spec_helper.rb
+spec/rails_helper.rb
+</pre>
+</div>
+
+Use the rspec command to run your specs:
+
+<div class="console"><pre>
+bundle exec rspec
+</pre>
+</div>
+
+By default the above will run all spec files in the spec directory. 
+
+To run only a subset of these specs use the following command:
+
+<div class="console"><pre>
+# Run only a specific folder name
+bundle exec rspec spec/folder_name
+
+# Run only specs for a specific type of test such as the post controller
+bundle exec rspec spec/controllers/post_controller_spec.rb
+</pre>
+</div>
+
+## RSpec Basics
+
+<div class="console"><pre>
+1 RSpec.describe Tree do
+2  it "is able to age by 1 year increments" do
+3    orange_tree = Tree.new
+4    orange_tree.age   
+5   expect(orange_tree.age).to eq(1)
+6  end
+7 end
+</pre>
+</div>
+
+The 'describe' and 'it' methods come from rspec-core. The Tree class would be from your code. You can think of 'describe' as a header to describe which class you are testing and 'it' as a string/subheader that states what specifically you are testing in the Tree class.
+
+The last line of the example expresses an expected outcome. If orange_tree.age == 1, then the example passes. If not, it fails with a message like:
+
+<div class="console">
+<pre>
+expected: #< Tree @age=1 >
+     got: #< Tree @age=0 >
+</pre>
+</div>
+
+## Matchers
+Remember in our example on line 5? 'to eq' is a matcher. RSpec has many built-in matchers. Matchers evaluates our expectations. In our example, we are saying that we expect orange_tree's age to equal an integer of 1.
+
+Check out the other built-in matchers!
+https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+
 
-  Bla bla bla.
 MARKDOWN
 
 next_step "types_of_tests"

sites/en/testing/what_are_tests.step

@@ -1,7 +1,23 @@
 message <<-MARKDOWN
-  What are tests?
+# What Are Tests?
+Tests are ways of testing our code to see if they are performing the way we have intended it behave.
+
+# Example
+ For example, lets say we wanted to create a program that models an orange tree.  Well, what defines an orange tree to us? Is it safe to say that we need at least two objects, an orange object and a tree object? Can our tree mature and bear more fruit at a certain age? Could our oranges ripen and fall from the tree?  Sounds like the list can become lengthy right? Lets stop here for a few minutes and see what we need to fulfill these user stories.  
+
+# What We Need To Test?
+Remember that we need to model an orange and a tree, so we know that there are two objects that needs to be created.
+
+We could say that the tree will not bear fruit until it matures at one year of age and then it well bare an X amount of oranges.  We would need a test to test if the tree ages and a test to see if the tree has created an X amount of oranges once it has matured.
+ 
+How do we determine if an orange is ripe? Well, we can have oranges age and if it is at least 30 days old, then it will fall from the tree.  We would need to write a test to check for ripeness and a test to check if it falls at ripeness.
+
+# Now That We Have Tests
+You could think of tests as a requirement list.  Every time a change is made we want to test to see if our code still meets those requirements. For example, as our program becomes increasingly complex and we want to have our tree to have a certain lifespan, would it make sense for our tree to continue to create oranges after exceeding that lifespan?   
+
+# Why Is It Important That We Test?
+For situations like our tree's lifespan is a prime example of why tests are important.  As our program become more complex over time the tests tells us that a basic requirement is not fulfilled and needs to be addressed.  Can you imagine looking at pages and pages of code that was written by someone else or many years ago without a way to trace exactly where the bug is?  Tests can help!
 
-  Bla bla bla.
 MARKDOWN
 
 next_step "testing_frameworks"