Sha256: 3ef92a28ee9a79cb9dadacd28d8ff7cbcebf52ada5d7379cf3d36e710b52cec5
Contents?: true
Size: 1.13 KB
Versions: 3
Compression:
Stored size: 1.13 KB
Contents
@disable-bundler Feature: Update minable files Scenario: Updating updates an existing minable install Given minable is already installed When I write to "minable/_minable.scss" with: """ foobar """ And I run `bundle exec minable update` Then the output should contain "Minable files updated." And the file "minable/_minable.scss" should not contain "foobar" Scenario: Updating with a --path option Given I install minable to "custom_path" When I write to "custom_path/minable/_minable.scss" with: """ foobar """ And I run `bundle exec minable update` Then the output should contain "No existing minable installation. Doing nothing." When I run `bundle exec minable update --path custom_path` Then the output should contain "Minable files updated." And the file "custom_path/minable/_minable.scss" should not contain "foobar" Scenario: Updating does not generate a new minable install And I run `bundle exec minable update` Then minable should not have been generated And the output should contain "No existing minable installation. Doing nothing."
Version data entries
3 entries across 3 versions & 1 rubygems
Version | Path |
---|---|
minable-0.1.1 | features/update.feature |
minable-0.0.2 | features/update.feature |
minable-0.0.1 | features/update.feature |