openproject/features/custom_fields/create_float.feature

#-- copyright
# OpenProject is a project management system.
#
# Copyright (C) 2012-2013 the OpenProject Team
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License version 3.
#
# See doc/COPYRIGHT.rdoc for more details.
#++

Feature: Localized decimal custom fields can be created

  Background:
    Given I am admin
    And the following languages are active:
      | en |
      | de |
    When I go to the custom fields page
    When I follow "New custom field" within "#tab-content-WorkUnitCustomField"

  @javascript
  Scenario: Creating a decimal custom field
    When I select "Float" from "custom_field_field_format"
    And I set the english localization of the "name" attribute to "New Field"
    And I set the english localization of the "default_value" attribute to "20.34"
    And I press "Save"
    Then I should be on the custom fields page
provide every possible file with a short copyright notice This was done using the rake task: rake copyright:update 12 years ago			`#-- copyright`
			`# OpenProject is a project management system.`
			`#`
			`# Copyright (C) 2012-2013 the OpenProject Team`
			`#`
			`# This program is free software; you can redistribute it and/or`
			`# modify it under the terms of the GNU General Public License version 3.`
			`#`
			`# See doc/COPYRIGHT.rdoc for more details.`
			`#++`

add features from coretests plugin as of revision 2f2aff7 of github remote 12 years ago			`Feature: Localized decimal custom fields can be created`

			`Background:`
			`Given I am admin`
			`And the following languages are active:`
			`\| en \|`
			`\| de \|`
			`When I go to the custom fields page`
Fix tests 12 years ago			`When I follow "New custom field" within "#tab-content-WorkUnitCustomField"`
add features from coretests plugin as of revision 2f2aff7 of github remote 12 years ago
			`@javascript`
			`Scenario: Creating a decimal custom field`
			`When I select "Float" from "custom_field_field_format"`
Attempt to fix custom_fields cukes Step definitions shouldn't react on page state, but always execute the same actions. Otherwise they need to wait a long time, only then they can be sure their decision is right. Normally, capybara waits for a specific event and only waits the full time when the event never occurs. Changed the 'I add the (.+) localization of the "(.+)" attribute as "(.+)"' step to only add localization attributes. It fails most of the time when used for changing an attribute. Adapted all cukes found failing through this. 12 years ago			`And I set the english localization of the "name" attribute to "New Field"`
			`And I set the english localization of the "default_value" attribute to "20.34"`
add features from coretests plugin as of revision 2f2aff7 of github remote 12 years ago			`And I press "Save"`
			`Then I should be on the custom fields page`