Skip to content

Commit

Permalink
Merge pull request #5074 from neos/task/format-behat-tests
Browse files Browse the repository at this point in the history 
TASK: Format behat tests
  • Loading branch information
@nezaniel
nezaniel committed May 19, 2024
2 parents 0243cf1 + e0e3d91 commit 9063c1d
Show file tree
Hide file tree
Showing 105 changed files with 1,812 additions and 1,809 deletions.
6 changes: 3 additions & 3 deletions ...res/Projection/ProjectionIntegrityViolationDetection/HierarchyIntegrityIsProvided.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,9 @@ Feature: Run integrity violation detection regarding hierarchy relations and nod
| newContentStreamId | "cs-identifier" |
And I am in workspace "live" and dimension space point {}
And the command CreateRootNodeAggregateWithNode is executed with payload:
| Key | Value |
| nodeAggregateId | "lady-eleonode-rootford" |
| nodeTypeName | "Neos.ContentRepository:Root" |
| Key | Value |
| nodeAggregateId | "lady-eleonode-rootford" |
| nodeTypeName | "Neos.ContentRepository:Root" |
And the event NodeAggregateWithNodeWasCreated was published with payload:
| Key | Value |
| workspaceName | "live" |
Expand Down
6 changes: 3 additions & 3 deletions ...jection/ProjectionIntegrityViolationDetection/NodesHaveAtMostOneParentPerSubgraph.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,9 @@ Feature: Run integrity violation detection regarding parent relations
| newContentStreamId | "cs-identifier" |
And I am in workspace "live" and dimension space point {"language":"de"}
And the command CreateRootNodeAggregateWithNode is executed with payload:
| Key | Value |
| nodeAggregateId | "lady-eleonode-rootford" |
| nodeTypeName | "Neos.ContentRepository:Root" |
| Key | Value |
| nodeAggregateId | "lady-eleonode-rootford" |
| nodeTypeName | "Neos.ContentRepository:Root" |
And the event NodeAggregateWithNodeWasCreated was published with payload:
| Key | Value |
| workspaceName | "live" |
Expand Down
6 changes: 3 additions & 3 deletions ...res/Projection/ProjectionIntegrityViolationDetection/ReferenceIntegrityIsProvided.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -24,9 +24,9 @@ Feature: Run integrity violation detection regarding reference relations
| newContentStreamId | "cs-identifier" |
And I am in workspace "live" and dimension space point {"language":"de"}
And the command CreateRootNodeAggregateWithNode is executed with payload:
| Key | Value |
| nodeAggregateId | "lady-eleonode-rootford" |
| nodeTypeName | "Neos.ContentRepository:Root" |
| Key | Value |
| nodeAggregateId | "lady-eleonode-rootford" |
| nodeTypeName | "Neos.ContentRepository:Root" |
And the event NodeAggregateWithNodeWasCreated was published with payload:
| Key | Value |
| workspaceName | "live" |
Expand Down
6 changes: 3 additions & 3 deletions ...ures/Projection/ProjectionIntegrityViolationDetection/SiblingsAreDistinctlySorted.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,9 @@ Feature: Run integrity violation detection regarding sibling sorting
| newContentStreamId | "cs-identifier" |
And I am in workspace "live" and dimension space point {"language":"de"}
And the command CreateRootNodeAggregateWithNode is executed with payload:
| Key | Value |
| nodeAggregateId | "lady-eleonode-rootford" |
| nodeTypeName | "Neos.ContentRepository:Root" |
| Key | Value |
| nodeAggregateId | "lady-eleonode-rootford" |
| nodeTypeName | "Neos.ContentRepository:Root" |

Scenario: Create two siblings and set the sorting to the same value
When the event NodeAggregateWithNodeWasCreated was published with payload:
Expand Down
6 changes: 3 additions & 3 deletions ...Features/Projection/ProjectionIntegrityViolationDetection/SubtreeTagsAreInherited.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,9 @@ Feature: Run integrity violation detection regarding subtree tag inheritance
| newContentStreamId | "cs-identifier" |
And I am in workspace "live" and dimension space point {"language":"de"}
And the command CreateRootNodeAggregateWithNode is executed with payload:
| Key | Value |
| nodeAggregateId | "lady-eleonode-rootford" |
| nodeTypeName | "Neos.ContentRepository:Root" |
| Key | Value |
| nodeAggregateId | "lady-eleonode-rootford" |
| nodeTypeName | "Neos.ContentRepository:Root" |

Scenario: Create nodes, disable the topmost and remove some restriction edges manually
When the event NodeAggregateWithNodeWasCreated was published with payload:
Expand Down
14 changes: 7 additions & 7 deletions ...Features/01-RootNodeCreation/02-CreateRootNodeAggregateWithNode_WithoutDimensions.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -75,18 +75,18 @@ Feature: Create a root node aggregate
| nodeTypeName | "Neos.ContentRepository:Root" |

When the command CreateRootNodeAggregateWithNode is executed with payload:
| Key | Value |
| nodeAggregateId | "nody-mc-nodeface" |
| Key | Value |
| nodeAggregateId | "nody-mc-nodeface" |
| nodeTypeName | "Neos.ContentRepository:AnotherRoot" |

Then I expect exactly 3 events to be published on stream "ContentStream:cs-identifier"
And event at index 2 is of type "RootNodeAggregateWithNodeWasCreated" with payload:
| Key | Expected |
| contentStreamId | "cs-identifier" |
| nodeAggregateId | "nody-mc-nodeface" |
| Key | Expected |
| contentStreamId | "cs-identifier" |
| nodeAggregateId | "nody-mc-nodeface" |
| nodeTypeName | "Neos.ContentRepository:AnotherRoot" |
| coveredDimensionSpacePoints | [[]] |
| nodeAggregateClassification | "root" |
| coveredDimensionSpacePoints | [[]] |
| nodeAggregateClassification | "root" |

Then I expect the node aggregate "lady-eleonode-rootford" to exist
And I expect this node aggregate to have no parent node aggregates
Expand Down
8 changes: 4 additions & 4 deletions ...or/Features/01-RootNodeCreation/05-CreateRootNodeAggregateWithNode_WithDimensions.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ Feature: Create a root node aggregate
| coveredDimensionSpacePoints | [{"language":"mul"},{"language":"de"},{"language":"en"},{"language":"gsw"}] |
| nodeAggregateClassification | "root" |
And event metadata at index 1 is:
| Key | Expected |
| Key | Expected |

Then I expect the node aggregate "lady-eleonode-rootford" to exist
And I expect this node aggregate to be classified as "root"
Expand Down Expand Up @@ -89,16 +89,16 @@ Feature: Create a root node aggregate
| nodeTypeName | "Neos.ContentRepository:Root" |

When the command CreateRootNodeAggregateWithNode is executed with payload:
| Key | Value |
| nodeAggregateId | "nody-mc-nodeface" |
| Key | Value |
| nodeAggregateId | "nody-mc-nodeface" |
| nodeTypeName | "Neos.ContentRepository:AnotherRoot" |

Then I expect exactly 3 events to be published on stream "ContentStream:cs-identifier"
And event at index 2 is of type "RootNodeAggregateWithNodeWasCreated" with payload:
| Key | Expected |
| contentStreamId | "cs-identifier" |
| nodeAggregateId | "nody-mc-nodeface" |
| nodeTypeName | "Neos.ContentRepository:AnotherRoot" |
| nodeTypeName | "Neos.ContentRepository:AnotherRoot" |
| coveredDimensionSpacePoints | [{"language":"mul"},{"language":"de"},{"language":"en"},{"language":"gsw"}] |
| nodeAggregateClassification | "root" |

Expand Down
10 changes: 5 additions & 5 deletions ...Behavior/Features/02-NodeCreation/01-CreateNodeAggregateWithNode_ConstraintChecks.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -143,11 +143,11 @@ Feature: Create node aggregate with node
| parentNodeAggregateId | "lady-eleonode-rootford" |
| nodeName | "document" |
When the command CreateNodeAggregateWithNode is executed with payload and exceptions are caught:
| Key | Value |
| nodeAggregateId | "nody-mc-nodeface" |
| nodeTypeName | "Neos.ContentRepository.Testing:Node" |
| parentNodeAggregateId | "lady-eleonode-rootford" |
| nodeName | "document" |
| Key | Value |
| nodeAggregateId | "nody-mc-nodeface" |
| nodeTypeName | "Neos.ContentRepository.Testing:Node" |
| parentNodeAggregateId | "lady-eleonode-rootford" |
| nodeName | "document" |

Then the last command should have thrown an exception of type "NodeNameIsAlreadyCovered"

Expand Down
10 changes: 5 additions & 5 deletions ...es/02-NodeCreation/02-CreateNodeAggregateWithNode_ConstraintChecks_WithDimensions.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -129,10 +129,10 @@ Feature: Create node aggregate with node
"""
# We don't run structure adjustments here on purpose
When the command CreateNodeAggregateWithNode is executed with payload and exceptions are caught:
| Key | Value |
| nodeAggregateId | "nody-mc-nodeface" |
| Key | Value |
| nodeAggregateId | "nody-mc-nodeface" |
| nodeTypeName | "Neos.ContentRepository.Testing:LeafNode" |
| parentNodeAggregateId | "sir-david-nodenborough" |
| originDimensionSpacePoint | {"example":"source"} |
| nodeName | "tethered" |
| parentNodeAggregateId | "sir-david-nodenborough" |
| originDimensionSpacePoint | {"example":"source"} |
| nodeName | "tethered" |
Then the last command should have thrown an exception of type "NodeNameIsAlreadyCovered"
78 changes: 39 additions & 39 deletions ...ehavior/Features/02-NodeCreation/03-CreateNodeAggregateWithNode_WithoutDimensions.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -224,16 +224,16 @@ Feature: Create node aggregate with node

Then I expect exactly 4 events to be published on stream "ContentStream:cs-identifier"
And event at index 3 is of type "NodeAggregateWithNodeWasCreated" with payload:
| Key | Expected |
| contentStreamId | "cs-identifier" |
| nodeAggregateId | "sir-nodeward-nodington-iii" |
| nodeTypeName | "Neos.ContentRepository.Testing:NodeWithoutTetheredChildNodes" |
| originDimensionSpacePoint | [] |
| Key | Expected |
| contentStreamId | "cs-identifier" |
| nodeAggregateId | "sir-nodeward-nodington-iii" |
| nodeTypeName | "Neos.ContentRepository.Testing:NodeWithoutTetheredChildNodes" |
| originDimensionSpacePoint | [] |
| succeedingSiblingsForCoverage | [{"dimensionSpacePoint":[],"nodeAggregateId":"sir-david-nodenborough"}] |
| parentNodeAggregateId | "lady-eleonode-rootford" |
| nodeName | "esquire" |
| initialPropertyValues | [] |
| nodeAggregateClassification | "regular" |
| parentNodeAggregateId | "lady-eleonode-rootford" |
| nodeName | "esquire" |
| initialPropertyValues | [] |
| nodeAggregateClassification | "regular" |

And I am in workspace "live" and dimension space point {}
And I expect node aggregate identifier "sir-nodeward-nodington-iii" and node path "esquire" to lead to node cs-identifier;sir-nodeward-nodington-iii;{}
Expand Down Expand Up @@ -297,38 +297,38 @@ Feature: Create node aggregate with node

Then I expect exactly 5 events to be published on stream "ContentStream:cs-identifier"
And event at index 2 is of type "NodeAggregateWithNodeWasCreated" with payload:
| Key | Expected |
| contentStreamId | "cs-identifier" |
| nodeAggregateId | "sir-david-nodenborough" |
| nodeTypeName | "Neos.ContentRepository.Testing:NodeWithTetheredChildNodes" |
| originDimensionSpacePoint | [] |
| succeedingSiblingsForCoverage | [{"dimensionSpacePoint":[],"nodeAggregateId":null}] |
| parentNodeAggregateId | "lady-eleonode-rootford" |
| nodeName | "node" |
| initialPropertyValues | {"text": {"value": "my default", "type": "string"}} |
| nodeAggregateClassification | "regular" |
| Key | Expected |
| contentStreamId | "cs-identifier" |
| nodeAggregateId | "sir-david-nodenborough" |
| nodeTypeName | "Neos.ContentRepository.Testing:NodeWithTetheredChildNodes" |
| originDimensionSpacePoint | [] |
| succeedingSiblingsForCoverage | [{"dimensionSpacePoint":[],"nodeAggregateId":null}] |
| parentNodeAggregateId | "lady-eleonode-rootford" |
| nodeName | "node" |
| initialPropertyValues | {"text": {"value": "my default", "type": "string"}} |
| nodeAggregateClassification | "regular" |
And event at index 3 is of type "NodeAggregateWithNodeWasCreated" with payload:
| Key | Expected |
| contentStreamId | "cs-identifier" |
| nodeAggregateId | "nody-mc-nodeface" |
| nodeTypeName | "Neos.ContentRepository.Testing:SubNode" |
| originDimensionSpacePoint | [] |
| succeedingSiblingsForCoverage | [{"dimensionSpacePoint":[],"nodeAggregateId":null}] |
| parentNodeAggregateId | "sir-david-nodenborough" |
| nodeName | "child-node" |
| initialPropertyValues | {"text": {"value": "my sub default", "type": "string"}} |
| nodeAggregateClassification | "tethered" |
| Key | Expected |
| contentStreamId | "cs-identifier" |
| nodeAggregateId | "nody-mc-nodeface" |
| nodeTypeName | "Neos.ContentRepository.Testing:SubNode" |
| originDimensionSpacePoint | [] |
| succeedingSiblingsForCoverage | [{"dimensionSpacePoint":[],"nodeAggregateId":null}] |
| parentNodeAggregateId | "sir-david-nodenborough" |
| nodeName | "child-node" |
| initialPropertyValues | {"text": {"value": "my sub default", "type": "string"}} |
| nodeAggregateClassification | "tethered" |
And event at index 4 is of type "NodeAggregateWithNodeWasCreated" with payload:
| Key | Expected |
| contentStreamId | "cs-identifier" |
| nodeAggregateId | "nodimus-prime" |
| nodeTypeName | "Neos.ContentRepository.Testing:SubSubNode" |
| originDimensionSpacePoint | [] |
| succeedingSiblingsForCoverage | [{"dimensionSpacePoint":[],"nodeAggregateId":null}] |
| parentNodeAggregateId | "nody-mc-nodeface" |
| nodeName | "grandchild-node" |
| initialPropertyValues | {"text": {"value": "my sub sub default", "type": "string"}} |
| nodeAggregateClassification | "tethered" |
| Key | Expected |
| contentStreamId | "cs-identifier" |
| nodeAggregateId | "nodimus-prime" |
| nodeTypeName | "Neos.ContentRepository.Testing:SubSubNode" |
| originDimensionSpacePoint | [] |
| succeedingSiblingsForCoverage | [{"dimensionSpacePoint":[],"nodeAggregateId":null}] |
| parentNodeAggregateId | "nody-mc-nodeface" |
| nodeName | "grandchild-node" |
| initialPropertyValues | {"text": {"value": "my sub sub default", "type": "string"}} |
| nodeAggregateClassification | "tethered" |

And I expect the node aggregate "lady-eleonode-rootford" to exist
And I expect this node aggregate to be classified as "root"
Expand Down

0 comments on commit 9063c1d

Please sign in to comment.