TheDude
/
openproject
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
OpenProject is the leading open source project management software.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
8935 Commits
139 Branches
203 Tags
1.2 GiB
Tag: Branch: Tree: 0fd3c645db
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0fd3c645db'
${ noResults }
openproject/features/custom_fields/create_text.feature

40 lines
1.5 KiB
Raw Normal View History Unescape

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: Text custom fields can be created
Background:
improve spec and cuke performance
11 years ago
Given I am already admin
add features from coretests plugin as of revision 2f2aff7 of github remote
12 years ago
And the following languages are active:
| en |
| de |
When I go to the custom fields page
Adapt references to work package
12 years ago
When I follow "New custom field" within "#tab-content-WorkPackageCustomField"
add features from coretests plugin as of revision 2f2aff7 of github remote
12 years ago
@javascript
Scenario: Creating a text custom field with multiple name and default_value localizations
When I select "Text" 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"
add features from coretests plugin as of revision 2f2aff7 of github remote
12 years ago
And I add the german localization of the "name" attribute as "Neues Feld"
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 "default_value" attribute to "default"
add features from coretests plugin as of revision 2f2aff7 of github remote
12 years ago
And I add the german localization of the "default_value" attribute as "Standard"
And I press "Save"
And I follow "New Field"
Then there should be the following localizations:
| locale | name | default_value |
| en | New Field | default |
| de | Neues Feld | Standard |
Scenario: Creating a custom field with one name
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 "Issue Field"
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