Skip to content
This repository has been archived by the owner on May 3, 2022. It is now read-only.

[Behat] Add Textline fieldtype BDD tests #552

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

miguelcleverti
Copy link

@miguelcleverti miguelcleverti commented Apr 18, 2016

PlatformUI Textline BDD tests. Feature file and behat suite added.

Six test were marker with a broken tag, five of them depends on another Context(ContentType Context) that will be added later, since we are still improving the general organization of the Behat code.

The other test marked as broken still need further work however I don't think we should block this PR because of it.

Also added to the runbehat.sh script the exclusion of not working tests.

depends on: ezsystems/BehatBundle#53

@miguelcleverti
Copy link
Author

@@ -2,4 +2,4 @@

cd $HOME/build/ezplatform

php bin/behat -vv --profile=platformui --tags='~@edge'
php bin/behat -vv --profile=platformui --tags='~@edge && ~@notWorking'
Copy link
Contributor

@andrerom andrerom Apr 25, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we already have a tag called @\broken, should use the same

@andrerom
Copy link
Contributor

andrerom commented Apr 25, 2016

+1 (however dependency in behat bundle needs to pass, and merge, and this then needs to pass, before merge here)

##
@javascript @common
Scenario: A Content of an Content Type that has a text line fieldtype must have a text field
Given a Content Type with an "text line" Field exists
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given a Content Type with a "Text Line" Field Definition exists ?
I would write our domain names with the first letter uppercased. Also, a Content Type is made of Field Definitions, not Fields

@miguelcleverti
Copy link
Author

@andrerom changed the notWorking tag to broken

@miguelcleverti
Copy link
Author

miguelcleverti commented Apr 26, 2016

@dpobel I made all the changes suggested that are specific to Text Line, I took note of the rest and will make a dedicated PR with those since they are related to FieldType Behat in general.

Scenario: A Content item of an Content Type that has a Text Line Field Definition must have a Text Line Field
Given a Content Type with an "text line" Field exists
When I create a content of this type
Then I should see a "text line" field
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe specify "input field" (form domain).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants