stuffer 0.0.1

data/.gitignore

@@ -0,0 +1,19 @@
+*.gem
+*.rbc
+.DS_Store
+._.DS_Store
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in stuffer.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2013 Matt Buckley
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,68 @@
+# Stuffer
+
+Combines factory_girl and capybara to automatically populate forms
+with factory_girl information<br>
+**Pull requests welcome. Make sure to submit a successful test**<br>
+**Submit a failing test with any bugs/issues**
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+    gem 'stuffer'
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install stuffer
+
+## Usage
+
+visit the page you want to fill with capybara i.e.
+    
+    visit new_user_path
+    
+load your factory into stuffer
+
+    Stuffer.factorize :factory_name
+    
+to automatically fill in all fields on the page
+
+    Stuffer.stuff
+    
+to fill in individual fields, stuffer currently supports input_fields, selections,
+checkboxes and radio buttons
+
+    Stuffer.fill :factory_field
+    Stuffer.select :factory_field
+    Stuffer.check :factory_field
+    Stuffer.radio :factory_field
+    
+don't forget to submit the form with capybara after Stuffer
+    
+    click_on 'Create user'
+    
+You can also use nested forms with stuffer.
+First factorize both the form and the nested form
+
+    Stuffer.factorize :factory_name, :nested_factory_name
+    
+It's important that the nested factory is supplied as the second argument
+You can then use stuffer just as you would with a single model
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request
+
+## Credit
+[capybara](https://github.com/jnicklas/capybara)<br>
+[FactoryGirl](https://github.com/thoughtbot/factory_girl)<br>
+[HeroicEric](https://github.com/HeroicEric)<br>
+[MattThousand](https://github.com/mattThousand)<br>

data/Rakefile

@@ -0,0 +1 @@
+require "bundler/gem_tasks"

data/lib/stuffer.rb

@@ -0,0 +1,138 @@
+require "stuffer/version"
+require 'capybara'
+require 'pry'
+
+module Stuffer
+  attr_reader :factory_fields, :capy_fields
+
+  def self.factorize (factory, nest_factory=nil)
+    @factory = factory
+    @id = []
+    @factory_convert = "#{@factory.to_s.downcase}_"
+    @factory_fields = FactoryGirl.attributes_for(factory)
+    @factory_fields.keys.each do |key|
+      @id << "#{@factory_convert + key.to_s}"
+    end
+    if nest_factory
+      get_nested nest_factory
+    end
+    super_field
+    get_fields
+  end
+
+  def self.super_field
+    @fields = {}
+    counter = 0
+    if @nested_fields
+      @stuffer = @factory_fields.merge(@nested_fields)
+    else
+      @stuffer = @factory_fields
+    end
+    @stuffer.values.each do |value|
+      @fields[@id[counter]] = value
+      counter += 1
+    end
+  end
+
+  def self.get_nested nest
+    @nest = nest
+    @nested_fields = FactoryGirl.attributes_for(nest)
+    @nested_fields.keys.each do |key|
+      @id << "#{@factory_convert+nest.to_s}_attributes_#{key.to_s}"
+    end
+  end
+
+  def self.get_fields
+    @capy_fields = {}
+    Capybara.visit Capybara.current_url
+    @id.each do |field|
+      begin
+        Capybara.page.find_field(field)
+      rescue
+        false
+      else
+        @capy_fields[field] = Capybara.page.find_field(field).tag_name
+      end
+    end
+    @capy_fields
+  end
+
+  def self.convert symbol
+    if !@nested_fields
+      symbol_field = "#{@factory_convert+symbol.to_s}"
+      if @fields.keys.include?(symbol_field)
+        symbol = symbol_field
+        symbol
+      end
+    else
+      symbol_field = "#{@factory_convert+symbol.to_s}"
+      symbol_nest = "#{@factory_convert+@nest.to_s}_attributes_#{symbol.to_s}"
+      if @fields.keys.include?(symbol_field)
+        symbol = symbol_field
+        symbol
+      elsif @fields.keys.include?(symbol_nest)
+        symbol = symbol_nest
+        symbol
+      end
+    end
+  end
+
+  def self.fill name
+    if name.is_a? Symbol
+      name = convert name
+    end
+    if @id.include?(name) && @capy_fields[name] == 'input'
+      Capybara.fill_in name, with: @fields[name]
+    end
+  end
+
+  def self.select selection
+    if selection.is_a? Symbol
+      selection = convert selection
+    end
+    if @id.include?(selection) && @capy_fields[selection] == 'select'
+      Capybara.select @fields[selection], from: selection
+    end
+  end
+
+  def self.check checkbox
+    if checkbox.is_a? Symbol
+      checkbox = convert checkbox
+    end
+    if @id.include?(checkbox) && @capy_fields[checkbox] == 'input'
+      Capybara.check checkbox
+    end
+  end
+
+  def self.radio value
+    if value.is_a? Symbol
+      value = convert value
+    end
+    if @id.include? value
+      Capybara.choose("#{value}_#{@fields[value]}")
+    end
+  end
+
+  def self.stuff
+    @id.each do |stuff|
+      if @capy_fields[stuff] == 'input' && @fields[stuff] != false && @fields[stuff] != true
+        fill stuff
+      elsif @capy_fields[stuff] == 'input'
+        check stuff
+      elsif @capy_fields[stuff] == 'select'
+        select stuff
+      else
+        begin
+          radio stuff
+        rescue
+          false
+        else
+          true
+        end
+      end
+    end
+  end
+
+
+
+end

data/lib/stuffer/version.rb

@@ -0,0 +1,3 @@
+module Stuffer
+  VERSION = "0.0.1"
+end

data/lib/teststuff/.gitignore

@@ -0,0 +1,15 @@
+# See http://help.github.com/ignore-files/ for more about ignoring files.
+#
+# If you find yourself ignoring temporary files generated by your text editor
+# or operating system, you probably want to add a global ignore instead:
+#   git config --global core.excludesfile ~/.gitignore_global
+
+# Ignore bundler config
+/.bundle
+
+# Ignore the default SQLite database.
+/db/*.sqlite3
+
+# Ignore all logfiles and tempfiles.
+/log/*.log
+/tmp

data/lib/teststuff/.rspec

@@ -0,0 +1,2 @@
+--color
+--format documentation

data/lib/teststuff/Gemfile

@@ -0,0 +1,49 @@
+source 'https://rubygems.org'
+
+gem 'rails', '3.2.13'
+
+# Bundle edge Rails instead:
+# gem 'rails', :git => 'git://github.com/rails/rails.git'
+
+gem 'sqlite3'
+gem 'pry'
+gem 'simple_form'
+
+
+# Gems used only for assets and not required
+# in production environments by default.
+group :assets do
+  gem 'sass-rails',   '~> 3.2.3'
+  gem 'coffee-rails', '~> 3.2.1'
+
+  # See https://github.com/sstephenson/execjs#readme for more supported runtimes
+  # gem 'therubyracer', :platforms => :ruby
+
+  gem 'uglifier', '>= 1.0.3'
+end
+
+gem 'jquery-rails'
+
+gem 'stuffer', :git => 'git@github.com:wannabefro/stuffer.git', :branch => 'master'
+
+group :test, :development do
+  gem 'rspec-rails'
+  gem 'capybara'
+  gem 'factory_girl_rails'
+  gem 'launchy'
+end
+
+# To use ActiveModel has_secure_password
+# gem 'bcrypt-ruby', '~> 3.0.0'
+
+# To use Jbuilder templates for JSON
+# gem 'jbuilder'
+
+# Use unicorn as the app server
+# gem 'unicorn'
+
+# Deploy with Capistrano
+# gem 'capistrano'
+
+# To use debugger
+# gem 'debugger'

data/lib/teststuff/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |   |   |-- images
+  |   |   |-- javascripts
+  |   |   `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   |-- assets
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   `-- cache
+  |       `-- assets
+  `-- vendor
+      |-- assets
+      |   |-- javascripts
+      |   `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.