Uploaded image for project: 'Magnolia Test Framework'
  1. Magnolia Test Framework
  2. 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.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Neutral Neutral
    • None
    • None

      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)

        Acceptance criteria

              Unassigned Unassigned
              cmeier Christoph Meier
              Foundation
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Work Started:

                  Bug DoR
                  Task DoD

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - Not Specified
                    Not Specified
                    Logged:
                    Time Spent - 5.5h
                    5.5h