[MGNLTEST-184] Editing a JCR-item with a space in the "name" property changes the jcr-node-name after saving - when done with via selenium. Created: 25/Oct/21  Updated: 09/Nov/23

Status: Selected
Project: Magnolia Test Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Christoph Meier Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: VN-Testing, artt
Remaining Estimate: Not Specified
Time Spent: 5.5h
Original Estimate: Not Specified

Attachments: File _personas.dummy-personas.yaml     File personas.dummy-personas.yaml    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: core-TF-features-bugs-improvements
Team: Foundation
Work Started:

 Description   

Editing a JCR-item with a space in the "name" property changes the jcr-node-name after saving - when done with via selenium. The bug has been found while editing a persona.

Note:

The "bug" appears when running the procedure with selenium in a UI-test.
But there is no issue when doing the procedure manually.

Steps to reproduce:

h4, Manually:

  • Import the bootstrap
  • Select the node
  • Change a property on the 2nd tab
  • Do not change the property "name" on the 1st tab.
  • save.

With manual procedure there is "no issue".

With a UI test:

-> Get the test from GIT

When doing it with the test (with selenium) -
the node /dummy-personas/new-guy becomes /dummy-personas/new-guy0

 

 


Developper note:

"We" (roman, cmeier) assume that "somewhere" must be another name with the same name ... leading to a new name of the edited JCR-item.
While debugging I have seen that {{NodeNameHelper#getUniqueName(session, parentPath, name)} was called,
indicating that there is "another" node with that name. But ... no idea why

to export persona-nodes as YAML - one must change the config of the JCR app.
(/.magnolia/admincentral#app:definitions-app:overview;apps~jcr-browser-app~subApps~browser~actions~exportYaml~availability~rules~notBinary~workspaces)

 ----

 
 

Attachments:

  • personas.dummy-personas.yaml -> bootstrap used for both manual and UI test
  • _personas.dummy-personas.yaml -> the "result" after the UI test ... when cleanup of the node is omitted. (changed the name to avoid attachment file name conflict on JIRA)

Generated at Mon Feb 12 07:46:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.