Skip to content

Commit

Permalink
4150 - Adjust new tests to workspace names
Browse files Browse the repository at this point in the history
  • Loading branch information
Bernhard Schmitt committed May 11, 2024
1 parent 44bd697 commit 07f031f
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 15 deletions.
18 changes: 9 additions & 9 deletions ...ehavioralTests/Tests/Behavior/Features/09-NodeRenaming/02-ChangeNodeAggregateName.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Feature: Change node aggregate name
| workspaceDescription | "The live workspace" |
| newContentStreamId | "cs-identifier" |
And the graph projection is fully up to date
And I am in the active content stream of workspace "live" and dimension space point {"example":"source"}
And I am in workspace "live" and dimension space point {"example":"source"}

And the command CreateRootNodeAggregateWithNode is executed with payload:
| Key | Value |
Expand Down Expand Up @@ -68,22 +68,22 @@ Feature: Change node aggregate name

And I expect the graph projection to consist of exactly 9 nodes

When I am in the active content stream of workspace "live" and dimension space point {"example": "general"}
When I am in workspace "live" and dimension space point {"example": "general"}
Then I expect node aggregate identifier "nody-mc-nodeface" and node path "parent-document/renamed-document" to lead to node cs-identifier;nody-mc-nodeface;{"example":"general"}
Then I expect node aggregate identifier "nodimus-prime" and node path "parent-document/renamed-document/tethered" to lead to node cs-identifier;nodimus-prime;{"example":"general"}
Then I expect node aggregate identifier "nodimus-mediocre" and node path "parent-document/renamed-document/tethered/grandchild-document" to lead to no node

When I am in the active content stream of workspace "live" and dimension space point {"example": "source"}
When I am in workspace "live" and dimension space point {"example": "source"}
Then I expect node aggregate identifier "nody-mc-nodeface" and node path "parent-document/renamed-document" to lead to node cs-identifier;nody-mc-nodeface;{"example":"source"}
Then I expect node aggregate identifier "nodimus-prime" and node path "parent-document/renamed-document/tethered" to lead to node cs-identifier;nodimus-prime;{"example":"source"}
Then I expect node aggregate identifier "nodimus-mediocre" and node path "parent-document/renamed-document/tethered/grandchild-document" to lead to node cs-identifier;nodimus-mediocre;{"example":"source"}

When I am in the active content stream of workspace "live" and dimension space point {"example": "spec"}
When I am in workspace "live" and dimension space point {"example": "spec"}
Then I expect node aggregate identifier "nody-mc-nodeface" and node path "parent-document/renamed-document" to lead to node cs-identifier;nody-mc-nodeface;{"example":"source"}
Then I expect node aggregate identifier "nodimus-prime" and node path "parent-document/renamed-document/tethered" to lead to node cs-identifier;nodimus-prime;{"example":"source"}
Then I expect node aggregate identifier "nodimus-mediocre" and node path "parent-document/renamed-document/tethered/grandchild-document" to lead to node cs-identifier;nodimus-mediocre;{"example":"source"}

When I am in the active content stream of workspace "live" and dimension space point {"example": "peer"}
When I am in workspace "live" and dimension space point {"example": "peer"}
Then I expect node aggregate identifier "nody-mc-nodeface" and node path "parent-document/renamed-document" to lead to node cs-identifier;nody-mc-nodeface;{"example":"peer"}
Then I expect node aggregate identifier "nodimus-prime" and node path "parent-document/renamed-document/tethered" to lead to node cs-identifier;nodimus-prime;{"example":"peer"}
Then I expect node aggregate identifier "nodimus-mediocre" and node path "parent-document/renamed-document/tethered/grandchild-document" to lead to no node
Expand Down Expand Up @@ -114,22 +114,22 @@ Feature: Change node aggregate name

And I expect the graph projection to consist of exactly 9 nodes

When I am in the active content stream of workspace "live" and dimension space point {"example": "general"}
When I am in workspace "live" and dimension space point {"example": "general"}
Then I expect node aggregate identifier "nody-mc-nodeface" and node path "parent-document/renamed-document" to lead to node cs-identifier;nody-mc-nodeface;{"example":"general"}
Then I expect node aggregate identifier "nodimus-prime" and node path "parent-document/renamed-document/tethered" to lead to node cs-identifier;nodimus-prime;{"example":"general"}
Then I expect node aggregate identifier "nodimus-mediocre" and node path "parent-document/renamed-document/tethered/grandchild-document" to lead to no node

When I am in the active content stream of workspace "live" and dimension space point {"example": "source"}
When I am in workspace "live" and dimension space point {"example": "source"}
Then I expect node aggregate identifier "nody-mc-nodeface" and node path "parent-document/renamed-document" to lead to node cs-identifier;nody-mc-nodeface;{"example":"source"}
Then I expect node aggregate identifier "nodimus-prime" and node path "parent-document/renamed-document/tethered" to lead to node cs-identifier;nodimus-prime;{"example":"source"}
Then I expect node aggregate identifier "nodimus-mediocre" and node path "parent-document/renamed-document/tethered/grandchild-document" to lead to node cs-identifier;nodimus-mediocre;{"example":"source"}

When I am in the active content stream of workspace "live" and dimension space point {"example": "spec"}
When I am in workspace "live" and dimension space point {"example": "spec"}
Then I expect node aggregate identifier "nody-mc-nodeface" and node path "parent-document/renamed-document" to lead to node cs-identifier;nody-mc-nodeface;{"example":"source"}
Then I expect node aggregate identifier "nodimus-prime" and node path "parent-document/renamed-document/tethered" to lead to node cs-identifier;nodimus-prime;{"example":"source"}
Then I expect node aggregate identifier "nodimus-mediocre" and node path "parent-document/renamed-document/tethered/grandchild-document" to lead to node cs-identifier;nodimus-mediocre;{"example":"source"}

When I am in the active content stream of workspace "live" and dimension space point {"example": "peer"}
When I am in workspace "live" and dimension space point {"example": "peer"}
Then I expect node aggregate identifier "nody-mc-nodeface" and node path "renamed-document" to lead to node cs-identifier;nody-mc-nodeface;{"example":"peer"}
Then I expect node aggregate identifier "nodimus-prime" and node path "renamed-document/tethered" to lead to node cs-identifier;nodimus-prime;{"example":"peer"}
Then I expect node aggregate identifier "nodimus-mediocre" and node path "renamed-document/tethered/grandchild-document" to lead to no node
12 changes: 6 additions & 6 deletions ...ontentRepository.BehavioralTests/Tests/Behavior/Features/NodeTraversal/Timestamps.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -149,32 +149,32 @@ Feature: Behavior of Node timestamp properties "created", "originalCreated", "la
| newNodeName | "a-renamed" |
And the graph projection is fully up to date
And I am in the active content stream of workspace "user-test" and dimension space point {"language":"de"}
And I am in workspace "user-test" and dimension space point {"language":"de"}
Then I expect the node "a" to have the following timestamps:
| created | originalCreated | lastModified | originalLastModified |
| 2023-03-16 13:00:00 | 2023-03-16 12:00:00 | 2023-03-16 14:00:00 | 2023-03-16 14:00:00 |
And I am in the active content stream of workspace "user-test" and dimension space point {"language":"ch"}
And I am in workspace "user-test" and dimension space point {"language":"ch"}
Then I expect the node "a" to have the following timestamps:
| created | originalCreated | lastModified | originalLastModified |
| 2023-03-16 13:00:00 | 2023-03-16 12:30:00 | 2023-03-16 14:00:00 | 2023-03-16 14:00:00 |
When I am in the active content stream of workspace "review" and dimension space point {"language":"de"}
When I am in workspace "review" and dimension space point {"language":"de"}
Then I expect the node "a" to have the following timestamps:
| created | originalCreated | lastModified | originalLastModified |
| 2023-03-16 13:00:00 | 2023-03-16 12:00:00 | | |
When I am in the active content stream of workspace "review" and dimension space point {"language":"ch"}
When I am in workspace "review" and dimension space point {"language":"ch"}
Then I expect the node "a" to have the following timestamps:
| created | originalCreated | lastModified | originalLastModified |
| 2023-03-16 13:00:00 | 2023-03-16 12:30:00 | | |
When I am in the active content stream of workspace "live" and dimension space point {"language":"de"}
When I am in workspace "live" and dimension space point {"language":"de"}
Then I expect the node "a" to have the following timestamps:
| created | originalCreated | lastModified | originalLastModified |
| 2023-03-16 13:00:00 | 2023-03-16 12:00:00 | | |
When I am in the active content stream of workspace "live" and dimension space point {"language":"ch"}
When I am in workspace "live" and dimension space point {"language":"ch"}
Then I expect the node "a" to have the following timestamps:
| created | originalCreated | lastModified | originalLastModified |
| 2023-03-16 13:00:00 | 2023-03-16 12:30:00 | | |
Expand Down

0 comments on commit 07f031f

Please sign in to comment.