Some extra generators for Padrino that us at Head use in everyday development, using ActiveRecord, MiniTest and Machinist.
Ruby
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
lib
test
.document
.gitignore
.travis.yml
Gemfile
Gemfile.lock
LICENSE.txt
README.md
Rakefile
VERSION
lazy-head-gen.gemspec

README.md

lazy-head-gen

Build Status

lazy-head-gen provides some extra generators for the Padrino framework. These are set to use ActiveRecord, MiniTest and Machinist as these are the libraries we normally use in development at Head.

Installation

gem install lazy-head-gen

In a Gemfile:

gem 'lazy-head-gen', :group => [:development, :test]

Padrino gotcha: You'll need to put the gem 'lazy-head-gen' requirement after gem 'padrino' in your Gemfile.

lazy-head-gen depends on Padrino being loaded before it can do its stuff.

Also you will need to add this gem for both :development and :test groups in your Gemfile. There are a few bundled test helper functions and assertions which are used by the test files that are generated.

Usage

Admin Controller Tests Generator

Generates a fully tested admin controller test for the 6 CRUD actions of a standard Padrino admin controller.

Usage:

padrino g admin_controller_test [name]

Options:

-r, [--root=ROOT] The root destination. Default: .

Example:

padrino g admin_controller_tests products

Scaffold Generator

Generates a fully tested Padrino resource scaffold

Usage:

padrino g scaffold [name]

Options:

-r, [--root=ROOT] The root destination. Default: .

-s, [--skip-migration] Specify whether to skip generating a migration

-a, [--app-path=APP_PATH] The application destination path. Default: /app

-m, [--model-path=MODEL_PATH] he model destination path. Default: .

-c, [--create-full-actions] Specify whether to generate basic (index and show) or full (index, show, new, create, edit, update and delete) actions.

Example:

padrino g scaffold Product title:string summary:text quantity:integer available_from:datetime display:boolean -c

Tests

First off you will need to add this line to your test_config.rb file, after you have required boot.rb.

include LazyHeadGen

This will allow you to access the login_as and assert_admin_not_logged_in methods used in the admin generated tests.

login_as

def login_as(account, password = "password", path = "/admin/sessions/create")
  post path, {
    :email => account.email, :password => password
  }
  follow_redirect!
end

alias :login_as_admin :login_as

This is also aliased as login_as_admin to avoid breaking any previously generated tests.

assert_admin_not_logged_in

def assert_admin_not_logged_in
  assert !last_response.ok?
  assert_equal 302, last_response.status
  assert_equal "http://example.org/admin/sessions/new", last_response.original_headers["Location"]
end

blueprints.rb

The scaffold and admin_controller_test generators are reliant on you using a machinist blueprints.rb file.

Changelog

0.6.X - Removed admin_url helper as it wasn't really needed. If you are using this in your tests you should change them to Admin.url (standard Padrino way of accessing URL's).

Also the syntax was incorrect for :create and :update URL's where the object had been put in the admin_url call. IE admin_url(:books, :create, :book => Book.make.attributes) should change to Admin.url(:books, :create), :book => Book.make.attributes

Changed login_as_admin to login_as, although is aliased so shouldn't break any previous tests.

0.5.X - Removed the shorthands for path, status etc because they weren't namespaced so they confliced with other tests and properties of objects...not good.

If you have been using them in your projects you will need to change them to the regular variables, ie last_response.status etc.

To Do List

  • Add form output to the scaffold generator
  • Add documentation for testing gem dependencies

Contributing to lazy-head-gen

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
  • Fork the project
  • Start a feature/bugfix branch
  • Commit and push until you are happy with your contribution
  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright

Copyright (c) 2012 Stuart Chinery and Dave Hrycyszyn - headlondon.com

See LICENSE.txt for further details.