Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TASK: Remove obsolete behat tests and outdated todos #4968

Draft
wants to merge 1 commit into
base: 9.0
Choose a base branch
from
Draft

TASK: Remove obsolete behat tests and outdated todos #4968

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 0 additions & 4 deletions ...Tests/Tests/Behavior/Features/03-NodeVariation/02-CreateNodeSpecializationVariant.feature
View file
Open in desktop
Expand Up @@ -414,10 +414,6 @@ Feature: Create node specialization
And I expect node aggregate identifier "nodimer-tetherton" and node path "document/tethered-node/tethered-leaf" to lead to node cs-identifier;nodimer-tetherton;{"market":"CH", "language":"de"}
And I expect node aggregate identifier "nody-mc-nodeface" and node path "document/child-document" to lead to node cs-identifier;nody-mc-nodeface;{"market":"DE", "language":"en"}

# @todo test based on NodeSpecializationVariantWasCreated ({"market":"CH", "language":"DE"})
# and VirtualNodeVariantWasRemoved ({"market":"CH", "language":"gsw"})
# to test that explicitly removed virtual variants are not implicitly created again

Scenario: Create specialization of node to dimension space point that is already covered
Given the command CreateNodeVariant is executed with payload:
| Key | Value |
Expand Down
372 changes: 0 additions & 372 deletions ...pository.BehavioralTests/Tests/Behavior/Features/NodeRemoval/RemoveNodesFromAggregate.wip
View file
Open in desktop

This file was deleted.

1 change: 0 additions & 1 deletion ...ts/Tests/Behavior/Features/NodeRetyping/ChangeNodeAggregateType_HappyPathStrategy.feature
View file
Open in desktop
Expand Up @@ -3,7 +3,6 @@ Feature: Change node aggregate type - behavior of HAPPYPATH strategy

As a user of the CR I want to change the type of a node aggregate.

# @todo change type to a type with a tethered child with the same name as one of the original one's but of different type
Background:
Given using the following content dimensions:
| Identifier | Values | Generalizations |
Expand Down
1 change: 0 additions & 1 deletion ...entRepository.BehavioralTests/Tests/Behavior/Features/NodeTraversal/AncestorNodes.feature
View file
Open in desktop
@@ -1,5 +1,4 @@
@contentrepository @adapters=DoctrineDBAL
# TODO implement for Postgres
Feature: Find and count nodes using the findAncestorNodes and countAncestorNodes queries

Background:
Expand Down
1 change: 0 additions & 1 deletion ...ontentRepository.BehavioralTests/Tests/Behavior/Features/NodeTraversal/ChildNodes.feature
View file
Open in desktop
@@ -1,5 +1,4 @@
@contentrepository @adapters=DoctrineDBAL
# TODO implement for Postgres
Feature: Find and count nodes using the findChildNodes and countChildNodes queries

Background:
Expand Down
1 change: 0 additions & 1 deletion ...ntentRepository.BehavioralTests/Tests/Behavior/Features/NodeTraversal/ClosestNode.feature
View file
Open in desktop
@@ -1,5 +1,4 @@
@contentrepository @adapters=DoctrineDBAL
# TODO implement for Postgres
Feature: Find nodes using the findClosestNode query

Background:
Expand Down
1 change: 0 additions & 1 deletion ...tRepository.BehavioralTests/Tests/Behavior/Features/NodeTraversal/DescendantNodes.feature
View file
Open in desktop
@@ -1,5 +1,4 @@
@contentrepository @adapters=DoctrineDBAL
# TODO implement for Postgres
Feature: Find and count nodes using the findDescendantNodes and countDescendantNodes queries

Background:
Expand Down
1 change: 0 additions & 1 deletion ...Repository.BehavioralTests/Tests/Behavior/Features/NodeTraversal/RetrieveNodePath.feature
View file
Open in desktop
@@ -1,5 +1,4 @@
@contentrepository @adapters=DoctrineDBAL
# TODO implement for Postgres
Feature: Find nodes using the retrieveNodePath query

Background:
Expand Down
1 change: 0 additions & 1 deletion ...ontentRepository.BehavioralTests/Tests/Behavior/Features/NodeTraversal/Timestamps.feature
View file
Open in desktop
@@ -1,5 +1,4 @@
@contentrepository @adapters=DoctrineDBAL
# TODO implement for Postgres
Feature: Behavior of Node timestamp properties "created", "originalCreated", "lastModified" and "originalLastModified"

Background:
Expand Down
2 changes: 1 addition & 1 deletion ...havioralTests/Tests/Behavior/Features/W7-WorkspacePublication/02-PublishWorkspace.feature
View file
Open in desktop
Expand Up @@ -139,7 +139,7 @@ Feature: Workspace based content publishing

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

# REBASING + Publishing: works now (TODO soft constraint check for old value)
# REBASING + Publishing: works now
When the command RebaseWorkspace is executed with payload:
| Key | Value |
| workspaceName | "user-test" |
Expand Down
46 changes: 0 additions & 46 deletions ...sts/Tests/Behavior/Features/W8-IndividualNodePublication/04-AllFeaturePublication.feature
View file
Open in desktop
Expand Up @@ -170,49 +170,6 @@ Feature: Publishing hide/show scenario of nodes
And I expect node aggregate identifier "nody-mc-nodeface" to lead to node user-cs-identifier-modified;nody-mc-nodeface;{}
And I expect node aggregate identifier "sir-nodeward-nodington-iii" to lead to node user-cs-identifier-modified;sir-nodeward-nodington-iii;{}


# @todo check why these won't run

#Scenario: (ChangeNodeAggregateName) It is possible to publish changing the node name.
# Given the command CreateWorkspace is executed with payload:
# | Key | Value |
## | workspaceName | "user-test" |
# | baseWorkspaceName | "live" |
# | newContentStreamId | "user-cs-identifier" |
# And the graph projection is fully up to date

# SETUP: change two node names in USER workspace
#Given the command "ChangeNodeAggregateName" is executed with payload:
# | Key | Value |
# | contentStreamId | "user-cs-identifier" |
# | nodeAggregateId | "sir-david-nodenborough" |
# | newNodeName | "text1mod" |
#Given the command "ChangeNodeAggregateName" is executed with payload:
# | Key | Value |
# | contentStreamId | "user-cs-identifier" |
# | nodeAggregateId | "sir-nodeward-nodington-iii" |
# | newNodeName | "imagemod" |
# And the graph projection is fully up to date

# When the command PublishIndividualNodesFromWorkspace is executed with payload:
# | Key | Value |
# | workspaceName | "user-test" |
# | nodesToPublish | [{"nodeAggregateId": "sir-david-nodenborough", "contentStreamId": "user-cs-identifier", "dimensionSpacePoint": {}}] |
#And the graph projection is fully up to date

# When I am in the active content stream of workspace "live" and dimension space point {}
## Then I expect the node aggregate "lady-eleonode-rootford" to have the following child nodes:
# | Name | nodeAggregateId |
# | text1mod | sir-david-nodenborough |
# | image | sir-nodeward-nodington-iii |

# When I am in the active content stream of workspace "user-test" and dimension space point {}
# Then I expect the node aggregate "lady-eleonode-rootford" to have the following child nodes:
# | Name | nodeAggregateId |
# | text1mod | sir-david-nodenborough |
# | imagemod | sir-nodeward-nodington-iii |


Scenario: (RemoveNodeAggregate) It is possible to publish a node removal
Given the command CreateWorkspace is executed with payload:
| Key | Value |
Expand Down Expand Up @@ -397,6 +354,3 @@ Feature: Publishing hide/show scenario of nodes
Then I expect node aggregate identifier "new1-agg" to lead to node user-cs-identifier-modified;new1-agg;{}
Then I expect node aggregate identifier "new2-agg" to lead to node user-cs-identifier-modified;new2-agg;{}


# TODO: implement MoveNodeAggregate testcase
# TODO: implement CreateNodeVariant testcase
122 changes: 0 additions & 122 deletions ....BehavioralTests/Tests/Behavior/Features/Workspaces/RemoveNodeAggregateWithDimensions.wip
View file
Open in desktop

This file was deleted.