rrgayhart

Module 4 Cheatsheet

Points

To graduate from Module 4 you will need to get ~80% of the total assigned points and pass your portfolio review. There will be ~1250 total points.

Everyone should have access to a google drive spreadsheet that lists where you're at in the pointwise.

If you don't have a link or the magic of google drive is on the fritz and your link isn't working, give us a shout.

rrgayhart

What's this PR do?

Where should the reviewer start?

How should this be manually tested?

Any background context you want to provide?

Screenshots (if appropriate)

What gif best describes this PR or how it makes you feel?

rrgayhart

Picking A Project to Work On

• Find a Repo that is primarily written in a language you're comfortable with.
  • Check out 24pullrequests.com
  • Talk to mentors that regularly contribute to open source for suggestions
  • Think about tools you already use like rspec or minitest.
  • Browse around Github
• Avoid 'dead' repos - look at open PRs for the project - if a ton unmerged, project may be dead. Also look at stars for the repo and last commit date on master.
• Look at the open issues for ones you can help with
• Look at coverage reports and builds for areas that are untested
• Fork the repo

rrgayhart

Use this gist to write down notes and questions as you read through the lesson plan. https://github.com/turingschool/lesson_plans/blob/master/ruby_04-apis_and_scalability/react_in_theory.markdown

What does React do?

It is a small view rendering library that works in components.

How does React interact with the DOM?

rrgayhart

Adding Sinon to WebPack

• Open your project (if you're using WebPack, obviously)

• npm install sinon --save-dev

• You should now have Sinon in your node modules and listed in your package.json file

• In your tests, require Sinon: var sinon = require('sinon');

rrgayhart

Step One: Watch Writing Testable JavaScript - Rebecca Murphey from Full Frontal 2012 (award for worst conference name ever?)

Step Two: Fork this gist.

Step Three: Consider the four responsibilities that Rebecca lists for client side code (hint: they're color coded).

• Did any of the responsibilities that she lists surprise you?
• Do you feel like you mentally split your client side code in IdeaBox and other past projects into these responsibilities?

Step Four: Totally Optional: take a look at some of the other forks and comment if the spirit moves you.

rrgayhart

This is an excellent post that explains a little bit behind the difficulty in testing external services https://robots.thoughtbot.com/how-to-stub-external-services-in-tests How to Stub External Services in Tests

One simple option is to use Webmock

Here is an example of using Webmock in a similar way to what VCR does - which is recording and reading from a file

stub_request(:any, "www.example.com").

rrgayhart

##PROTIP: README Love

READMEs are AWESOME. They are one of the best things you can add to a repo, (other than quality code), to make it look professional.

####Things that make a README great:

• A link to the production site on heroku
• A screenshot (or a few) of what the app does (This is especially important if you don't have the production app up and running yet)
• Directions on how to clone or fork the repo and run it locally (explain it like you're explaining things to a totally new programmer)

rrgayhart

development and test gems
----------------------------------------------

group :development, :test do
  gem 'sqlite3'
  gem 'rspec-rails'
  gem "capybara"
  gem 'selenium-webdriver'
  gem 'shoulda-matchers'
  gem 'launchy'

rrgayhart

Simon
https://github.com/srt32
http://www.simontaranto.com/

Louisa
https://github.com/LouisaBarrett
http://www.linkedin.com/in/louisabarrett

Kevin
https://github.com/x46672