Sha256: cdd0c34ec877cc640d3824563aeb694663fb600320bc4b4fa41094821881c40f

Contents?: true

Size: 953 Bytes

Versions: 14

Compression:

Stored size: 953 Bytes

Contents

Feature: Migration

  Background:
    Given I generate a new rails application
    And I generate a "User" model:

  Scenario: Vintage syntax
    Given I run a paperclip migration to add a paperclip "attach" to the "User" model

    And I run a migration
    Then I should have attachment columns for "attach"

    When I rollback a migration
    Then I should not have attachment columns for "attach"

  Scenario: New syntax with create_table
    Given I run a paperclip migration to add a paperclip "attach" to the "User" model

    And I run a migration
    Then I should have attachment columns for "attach"

  Scenario: New syntax outside of create_table
    Given I run a paperclip migration to add a paperclip "attachment_sample" to the "User" model

    And I run a migration
    Then I should have attachment columns for "attachment_sample"

    When I rollback a migration
    Then I should not have attachment columns for "attachment_sample"

Version data entries

14 entries across 14 versions & 1 rubygems

Version Path
kt-paperclip-7.2.2 features/migration.feature
kt-paperclip-7.2.1 features/migration.feature
kt-paperclip-7.2.0 features/migration.feature
kt-paperclip-6.4.2 features/migration.feature
kt-paperclip-7.1.1 features/migration.feature
kt-paperclip-7.1.0 features/migration.feature
kt-paperclip-7.0.1 features/migration.feature
kt-paperclip-7.0.0 features/migration.feature
kt-paperclip-6.4.1 features/migration.feature
kt-paperclip-6.4.0 features/migration.feature
kt-paperclip-6.3.0 features/migration.feature
kt-paperclip-6.2.2 features/migration.feature
kt-paperclip-6.2.1 features/migration.feature
kt-paperclip-6.2.0 features/migration.feature