-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Note that the test(s) requested by this ticket have been executed manually so far in the context of pre-release QA.
Create integration tests to ensure that using UTF-8 chars in page names / node names works fine.
High level scenarios
- Creating a page with a page name with UTF-8 chars
- Requesting a page with UTF-8 chars in the path to the page. * Publishing a page
- Publishing a page with UTF-8 chars in in its node name.
Scenario descriptions:
Scenario: Creating a page with UTF-8 chars in the page name. Given user Eric opens the pages app. When Eric creates a new page with the page name "С Новым Годом". Then the pages app contains the row with the label "С Новым Годом". And the JCR workspace pages contains the node "/С-Новым-Годом". Scenario: Requesting a page with UTF-8 chars in the path to the page. Given the page with the node name "Алекса́ндр-Серге́евич-Пу́шкин" exists. When requesting the URL "$context/Алекса́ндр-Серге́евич-Пу́шкин.html". Then Magnolia returns with HTTP response code 200. Scenario: Publishing a page with UTF-8 chars in in its node name. Given the page with the path "/ÜberÄrger" exist on the author context. When publishing the page "/ÜberÄrger". Then requesting "/ÜberÄrger" on the public context returns with HTTP response code 200.
The 3 tests can be added to info.magnolia.functionaltests.PagesCoreFunctionalTests
Acceptance criteria
- depends upon
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- mentioned in
-
Page Loading...
