Sha256: 052a90c68fe60a2e1e884151c737ec85ee59f9cfb755900e1c4c2fe9840a2178

Contents?: true

Size: 499 Bytes

Versions: 6

Compression:

Stored size: 499 Bytes

Contents

@cli
Feature: Upgrade Module from 3.1.x to 3.4.x

  Background:
    Given I am working on a BrowserCMS v3.1.x module named "bcms_widgets"

  Scenario: Verify Project
    Then a file named "script/console" should exist

  Scenario: Upgrade a Module from 3.1.x to 3.4.x
    When I run `bcms-upgrade module`
    Then the output should contain "Upgrading to BrowserCMS 3.3.x"
    And a Gemfile should be created
    And the engine should be created
    And the installation script should be created




Version data entries

6 entries across 6 versions & 1 rubygems

Version Path
browsercms-3.4.2 features/commands/upgrade_modules_to_3_4_0_from_3_1_x.feature
browsercms-3.4.2.rc1 features/commands/upgrade_modules_to_3_4_0_from_3_1_x.feature
browsercms-3.4.1 features/commands/upgrade_modules_to_3_4_0_from_3_1_x.feature
browsercms-3.4.0 features/commands/upgrade_modules_to_3_4_0_from_3_1_x.feature
browsercms-3.4.0.rc2 features/commands/upgrade_modules_from_3_1_to_3_4.feature
browsercms-3.4.0.rc1 features/commands/upgrade_modules_from_3_1_to_3_4.feature