https://github.com/appfolio/inheritable_fixtures

Simplify fixtures for a large Rails application which is split into multiple engines.
https://github.com/appfolio/inheritable_fixtures

Last synced: about 2 months ago
JSON representation

Simplify fixtures for a large Rails application which is split into multiple engines.

• Host: GitHub
• URL: https://github.com/appfolio/inheritable_fixtures
• Owner: appfolio
• Created: 2015-07-14T07:22:22.000Z (over 9 years ago)
• Default Branch: master
• Last Pushed: 2024-05-22T20:54:06.000Z (7 months ago)
• Last Synced: 2024-05-22T23:43:19.237Z (7 months ago)
• Language: Ruby
• Homepage:
• Size: 56.6 KB
• Stars: 2
• Watchers: 67
• Forks: 1
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# InheritableFixtures

[![GitHub version](https://badge.fury.io/gh/appfolio%2Finheritable_fixtures.svg)](http://badge.fury.io/gh/appfolio%2Finheritable_fixtures)

[![Build Status](https://travis-ci.org/appfolio/inheritable_fixtures.svg?branch=master)](https://travis-ci.org/appfolio/inheritable_fixtures)

Allows Rails engines to contain fixtures for their models and for those fixtures to be automatically used in the downstream engines. This is very much in line with Rails engines containing db migrations for their models and for those [migrations to be automatically used by the downstream engines](http://pivotallabs.com/leave-your-migrations-in-your-rails-engines/).

## Installation

Add this line to your application's `Gemfile`:

```ruby

gem 'inheritable_fixtures'

```

And then execute:

    $ bundle install

## Usage

This gem introduces a configuration option called `Rails.application.config.fixtures_paths`, which is by default empty. The list of fixtures is determined by traversing all the `fixtures_paths` looking for fixture files. `Rails.root.join('test/fixtures')` is always prepended to the list, thus it has the highest precedence.

When the application initializes, each engine adds `lib/fixtures` to the list (if that path exists).

### fixtures :all

Tests use `fixtures :all` or something like `fixtures :users, :addresses` to initial the database with necessary test data. It will now search for the fixtures in all `fixtures_paths`.

 

### fixture\_file\_upload

The `fixture_file_upload` is a handy utility provided by Rails for creating `Rack::Test::UploadedFile` out of a fixture file. It will now look for the fixture in all `fixtures_paths`.

### rake db:fixtures:load

The `db:fixtures:load` task is used to populate a database with the fixtures. It will now load all fixtures from `fixtures_paths`.

## Contributing

1. Fork it ( https://github.com/[my-github-username]/inheritable_fixtures/fork )

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 a new Pull Request