I'm Jason, a web application developer in East Tennessee.

Generating Test File Stubs for Existing Models, Views, and Controllers

I’ve noticed that if you install certain testing gems, like Factory Girl, or Rspec, that your Rails application will create test files for these libraries instead of using the defaults. Even further you can configure the generators used by your Rails app in /config/application.rb

# Configure generators values. Many other options are available,
# be sure to check the documentation.

config.generators do |g|
  g.stylesheets false
  g.test_framework :rspec
  g.fallbacks[:rspec] = :test_unit
  g.fixture_replacement :factory_girl

I’ve been anxious however in deciding which testing tools to learn and use with my project. If I choose the wrong one, then all the scaffold generated test code will be generated for the test framework I might choose to quit using at some point.

This is not completely correct though, as I’ve discovered.

I found that the following commands will generate the empty spec files.

rails generate rspec:model

rails generate rspec:view

rails generate rspec:controller

Even better though, if you’re looking for scaffold style files to be put in place, use the following syntax to generate scaffold code.

rails generate rspec:scaffold Post title:string body:text

If you decide to use basic Test::Unit based tests, instead of going with Rspec, you can also reconfigure your app to use Test::Unit again with generators, and then use the rake commands to generate the files that were generated via rspec.

$ rails g

Usage: rails generate GENERATOR [args] [options]

General options:

  -h, [--help]     # Print generator's options and usage
  -p, [--pretend]  # Run but do not make any changes
  -f, [--force]    # Overwrite files that already exist
  -s, [--skip]     # Skip files that already exist
  -q, [--quiet]    # Suppress status output

Please choose a generator below.

comments powered by Disqus