-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
-
6.2 Ramp-up 17, 6.2 Ramp-up 18
-
8
Write the functional tests for the Pages-app core functions with the medium prio:
Tests to add
- Add sub-page
- Delete single page
- Move component
- Publish page incl. subpages
- Unpublish page
- Publish deletion of single page
- Restore version
- Restore previous version
Depending on DEV-1349
- Publish & verify actual publication
- Also check the content which has been published, not just the page.
- Unpublish & verify actual unpublication
- verify that the rendered page is indeed no longer reachable, yields 404
- Publish deletion & verify unpublication
- verify that the rendered page is indeed no longer reachable, yields 404
Scope
- Implement all the tests which do not rely on
DEV-1349 - For those dep. on
DEV-1349, ... at least make sure we have empty methods with the javadoc with the "gherkin instructions".
How-To:
- The tests go into to the class info.magnolia.functionaltests.PagesCoreFunctionalTests
- Add a javadoc comment to each method using Gherkin syntax.
- See existing examples in the given class.
- Read Coding and commenting style for new integration tests
- Check the docu if required
- For API usage examples see examples in info.magnolia.testframework.selftest.*
- User for tests: Login with
- peter or eric when doing editing or publishing related tasks.
- To check / verify, the user typically doesn't matter
- instead of superuser use armin (Personas.ARMIN)
Acceptance criteria
- depends upon
-
MGNLTEST-19 Page object for rendered pages
- Closed
-
MGNLTEST-42 Page object for page editor (Pages app)
- Closed