Integer BDD Scenarios #234
Conversation
|
ping @bdunogier, @dpobel, @andrerom |
| Scenario: The label of an mandatory integer field of a Content must be marked as mandatory | ||
| Given a Content Type with a required "integer" with field definition name "Quantity" exists | ||
| When I create a content of this type | ||
| Then the "Quantity" field should be marked as mandatory |
There was a problem hiding this comment.
do we call it mandatory, or do we call it required?
|
ping @bdunogier, @andrerom |
|
+1 But for other field types we don't need to test everything, it is cool that we do it on one to be able to test FieldType features in general as well, but as said in #243 (comment) we should right now focus on generic use cases to cover all features widely, as opposed to deeply and build up backlog of what to do next to have deeper coverage. Any idea why this fails btw? |
|
+1 |
|
@andrerom can this be merged? |
|
According to todo implement is not done, if you mean it is ready to be merged there should not be a open sub task on the PR ;) |
|
@andrerom my mistake the implementation has been merged for some time now. |
|
+1 :) |
Following up the integer BDD scenarios form dropped PR #211
Todo: