status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
consul/ui-v2/tests/acceptance/components/text-input.feature

29 lines
690 B
Gherkin
Raw Normal View History

Use html5 oninput instead of onkeyup for native textual inputs This enables people to enter things using the mouse to paste for example, plus possible other things. As an aside it also answers my query regarding `fillIn` for testing, nothing needs to be actually _typed_ anymore! Doh
2018-07-03 14:40:15 +00:00
@setupApplicationTest
Add some low hanging intention tests, basically add intentions to others 1. There are various things tests that can just have intentions added into them, like filters and such like, add intentions to these 2. Start thinking about being able to negate steps easily, which will lead on to a cleanup of the steps
2018-07-04 12:21:30 +00:00
Feature: components / text-input: Text input
Use html5 oninput instead of onkeyup for native textual inputs This enables people to enter things using the mouse to paste for example, plus possible other things. As an aside it also answers my query regarding `fillIn` for testing, nothing needs to be actually _typed_ anymore! Doh
2018-07-03 14:40:15 +00:00
Background:
Given 1 datacenter model with the value "dc-1"
Scenario:
ui: Turn off the code editor whilst making an edit during testing (#4668) Having the code editor on removes the text area from the DOM, making it more difficult to enter text in the text editor during testing. This turns the code editor off whilst making edits during testing. No changes to UI code
2018-09-20 09:36:30 +00:00
When I visit the kv page for yaml
Use html5 oninput instead of onkeyup for native textual inputs This enables people to enter things using the mouse to paste for example, plus possible other things. As an aside it also answers my query regarding `fillIn` for testing, nothing needs to be actually _typed_ anymore! Doh
2018-07-03 14:40:15 +00:00
---
dc: dc-1
---
ui: Turn off the code editor whilst making an edit during testing (#4668) Having the code editor on removes the text area from the DOM, making it more difficult to enter text in the text editor during testing. This turns the code editor off whilst making edits during testing. No changes to UI code
2018-09-20 09:36:30 +00:00
Then the url should be /dc-1/kv/create
# Turn the Code Editor off so we can fill the value easier
And I click "[name=json]"
Use html5 oninput instead of onkeyup for native textual inputs This enables people to enter things using the mouse to paste for example, plus possible other things. As an aside it also answers my query regarding `fillIn` for testing, nothing needs to be actually _typed_ anymore! Doh
2018-07-03 14:40:15 +00:00
Then I fill in with json
---
ui: Turn off the code editor whilst making an edit during testing (#4668) Having the code editor on removes the text area from the DOM, making it more difficult to enter text in the text editor during testing. This turns the code editor off whilst making edits during testing. No changes to UI code
2018-09-20 09:36:30 +00:00
{"additional": "hi", "value": "there"}
---
Then I see submitIsEnabled
Scenario:
When I visit the acl page for yaml
---
dc: dc-1
---
Then the url should be /dc-1/acls/create
Then I fill in with json
---
{"name": "hi"}
Use html5 oninput instead of onkeyup for native textual inputs This enables people to enter things using the mouse to paste for example, plus possible other things. As an aside it also answers my query regarding `fillIn` for testing, nothing needs to be actually _typed_ anymore! Doh
2018-07-03 14:40:15 +00:00
---
Then I see submitIsEnabled