skill-assessment-app

History

Mark Moser 4bbd93ded1 rubocop noise: fixes FrozenStringLiteralComment Adding the .ruby-verison file triggered previously un-run cops, specifically: This cop is designed to help upgrade to Ruby 3.0. It will add the comment `# frozen_string_literal: true` to the top of files to enable frozen string literals. Frozen string literals will be default in Ruby 3.0. The comment will be added below a shebang and encoding comment. The frozen string literal comment is only valid in Ruby 2.3+. More info on rubocop [Automatic-Corrections](https://github.com/bbatsov/rubocop/wiki/Automatic-Corrections)		2016-09-08 10:30:13 -05:00
..
answer_validatable.rb	rubocop noise: fixes FrozenStringLiteralComment	2016-09-08 10:30:13 -05:00
email_validatable.rb	rubocop noise: fixes FrozenStringLiteralComment	2016-09-08 10:30:13 -05:00
input_options_validatable.rb	rubocop noise: fixes FrozenStringLiteralComment	2016-09-08 10:30:13 -05:00
README.txt	split up answer validation test into themed files	2016-08-16 12:08:13 -05:00

README.txt

Use this folder to store mocks, stubs, etc to make isolated testing possible.

Some definitions borrowed from:
http://martinfowler.com/articles/mocksArentStubs.html

* Dummy
  objects are passed around but never actually used.
  Usually they are just used to fill parameter lists.

* Fake
  objects actually have working implementations, but usually
  take some shortcut which makes them not suitable for
  production (an in memory database is a good example).

* Stubs
  provide canned answers to calls made during the test,
  usually not responding at all to anything outside what's
  programmed in for the test. Stubs may also record information
  about calls, such as an email gateway stub that remembers the
  messages it 'sent', or maybe only how many messages it 'sent'.

* Mocks
  objects pre-programmed with expectations which form a
  specification of the calls they are expected to receive.