factory_inspector 0.0.1 → 0.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. data/README.md +11 -10
  2. data/factory_inspector.gemspec +1 -1
  3. data/lib/factory_inspector/version.rb +1 -1
  4. metadata +2 -2
data/README.md CHANGED
@@ -1,16 +1,17 @@
1
1
  # FactoryInspector
2
2
 
3
- This very simple gem reports on how FactoryGirl factories
3
+ This very simple gem reports on how
4
+ [FactoryGirl](https://github.com/thoughtbot/factory_girl)
4
5
  are being used during your test runs. This is useful in
5
6
  understanding where the time is going during your test
6
7
  runs - while FactoryGirl is useful, overuse can lead to
7
- serious slowdowns to a cascade of database writes when
8
- building a test object.
8
+ serious slowdowns due to a cascade of database writes when
9
+ building test objects. The analysis relies on the changes
10
+ brought in with [FactoryGirl 3.2](http://robots.thoughtbot.com/post/21719164760/factorygirl-3-2-so-awesome-it-needs-to-be-released)
9
11
 
10
- This is a developer's tool; the Gem makes no effort to
11
- sanitize inputs or help you avoid making mistakes. It
12
- relies on the changes brought in with FactoryGirl 3.2:
13
- http://robots.thoughtbot.com/post/21719164760/factorygirl-3-2-so-awesome-it-needs-to-be-released
12
+ This gem is a developer utility and makes no effort to
13
+ sanitize inputs or help you avoid making mistakes, but
14
+ hopefully it's too simple to need much of that!
14
15
 
15
16
  ## Installation
16
17
 
@@ -28,10 +29,10 @@ Or install it yourself as:
28
29
 
29
30
  ## Usage
30
31
 
31
- FactoryInspector's API is just two methods - `start_inspection` and `generate_report`.
32
+ FactoryInspector's API is just two methods; `start_inspection` and `generate_report`
32
33
 
33
- Let's take a hypothetical `spec/spec_helper.rb` on a RSpec based
34
- project; the changes to use FactoryInspector would be:
34
+ Assuming you're on a RSpec based project, the changes to your
35
+ `spec/spec_helper.rb` file to introduce FactoryInspector would be:
35
36
 
36
37
  ```ruby
37
38
  require 'factory_inspector'
data/factory_inspector.gemspec CHANGED
@@ -6,7 +6,7 @@ Gem::Specification.new do |gem|
6
6
  gem.email = ["david.kennedy@examtime.com"]
7
7
  gem.description = %q{This very simple gem generates reports on how FactoryGirl factories are being used in your test runs.}
8
8
  gem.summary = %q{Reports on how FactoryGirl is used in test runs.}
9
- gem.homepage = ""
9
+ gem.homepage = "https://github.com/ExamTime/factory_inspector"
10
10
 
11
11
  gem.files = `git ls-files`.split($\)
12
12
  gem.executables = gem.files.grep(%r{^bin/}).map{ |f| File.basename(f) }
data/lib/factory_inspector/version.rb CHANGED
@@ -1,3 +1,3 @@
1
1
  module FactoryInspector
2
- VERSION = "0.0.1"
2
+ VERSION = "0.0.2"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: factory_inspector
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.1
4
+ version: 0.0.2
5
5
  prerelease:
6
6
  platform: ruby
7
7
  authors:
@@ -80,7 +80,7 @@ files:
80
80
  - lib/factory_inspector/report.rb
81
81
  - lib/factory_inspector/version.rb
82
82
  - spec/report_spec.rb
83
- homepage: ''
83
+ homepage: https://github.com/ExamTime/factory_inspector
84
84
  licenses: []
85
85
  post_install_message:
86
86
  rdoc_options: []