Its class-level Javadoc matches the manual test's intent exactly: "Tests that the create action and UI properly create Nested Documents at various levels in the hierarchy." (since 7.2RC1).
The manual test builds a hierarchy (a/b/c/d/e/f/g/h), navigates to an intermediate page and creates a child from it. The IT covers this across a hierarchy A -> A/B -> A/B/C -> A/B/C/D -> A/B/C/D/E -> ...:
createNestedDocumentsFromUI() (@Order(2)) is the closest match. Starting from the Home page, it repeatedly clicks the Create button and fills the create form with a parent space reference plus page name, creating a child page at each level of the hierarchy (child of a top-level page, child of a child, etc.), verifying breadcrumb/title/reference each time.
createNestedDocumentsFromURL() (@Order(1)) creates the same nested documents by navigating to their URL and clicking "Edit this page to create".
It also covers cases the manual test does not spell out: a child of a non-existing intermediate page (A/B/C/D/E/F/G, where F does not exist) and a child of a non-existing top-level page (X/Y).
So creating a child page from an intermediate page inside a nested-spaces hierarchy is fully covered — the automated test is actually broader than the manual one. No new automated test is needed.
Vincent Massol on 22/Jul/26 11:06
Ilie Andriuta please mark as already automated and don't execute any more manually Thx
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.