adding a follow and unfollow button partials.  The follow partial uses a hidden html field so that the form submits.  both use a form_for(model object.method) to manipulate the relationship model object.  One builds and one deletes.  The build one has a hidden html field to pass the :followed_id parameter.  The unfollow has an extra parameter to identify the html method (delete) b/c default is post.
renamed a file that was misspelled
testing to ensure that a user is signed in before they can visit the following page or the followers page.  uses a describe block inside a bunch of nested blocks that has an unsigned in user, and before visits teh following_user_path(user) and the followers_user_path(user) and checks the title of the page
created tests in the users requests (the users controller handles these) to check the following and followers pages.  On teh followed users pages it checks to see that if they follow someone that that person shows up in their followed users pages.  On the followers page, it checks to see that if someone signed up to follow them that they show up as a follower on the followers pages.
created teh following and followers routes in teh users controller.  Applied the before_filter signed_in_user to both pages by adding them to the filter array.  For following found the @user.followed_users and chained the .paginate(page: paraams[:page]) method to creates the @users array for the page the use later to render.  Of course, found the @user by using User.find(params[:id]) method, and passed a title using a simple assignmend to @title - which is cool b/c we did this in the controller - not sure if that's good code, but good to know it can be done.  then rendered teh show_follow - which haven't made yet.  Also note the @users array was different for followers, it used the .followers method, but still passed teh same paginate chain to create the @users array
created teh view for teh followers and user_following actions.  used teh gravatar_for helper function to render the gravatar, used an @user call to link to the user profile b/c rails interpretes that nicely, used a @user.microposts.count command to get a number of user microposts, user a @users.any? command to check the @users array that was generated in teh controller to see if there is ann array of followers or user_following respectively - depending on which page it is, which is actually handled by the controller, madea  second call to the gravatar_for helper to render all the followers or user_following people, rendered the title, and then made one final call to render @users, which has some rails magic that I don't quite get :)
added testing for the follow and unfollow buttons on the user profile page.  created another user, other_user and then inherited user b/c inside the user_pages_spec, using factory girl of coure, then signed in and did some tests.  for following a user i visited teh user path of teh other user, clicked their button to follow, and checked that it changed the followed_users count and then checked that it changed teh other_user.followers, and then checked the button to make sure that it's value toggled back and forth from follow to unfollow appropriated.  for the unfollow user first i followed the other user, visited that page, then clicked the unfollow button, checked the count of the users follower_users, checked the count of the other users followers, and checked teh button toggled.