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.
7656 Commits
139 Branches
203 Tags
1.2 GiB
Tag: Branch: Tree: d818f09f9c
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'd818f09f9c'
${ noResults }
openproject/features/custom_fields/create_int.feature

18 lines
610 B
Raw Normal View History Unescape

add features from coretests plugin as of revision 2f2aff7 of github remote
12 years ago
Feature: Int 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 custom fields cukes when using standard capybara find
12 years ago
When I follow "New custom field" within "#tab-content-IssueCustomField"
add features from coretests plugin as of revision 2f2aff7 of github remote
12 years ago
@javascript
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
Scenario: Creating an int custom field
add features from coretests plugin as of revision 2f2aff7 of github remote
12 years ago
When I select "Integer" 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 "342"
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