[MGNLTEST-52] Provide self-tests for high-order page objects Created: 03/Sep/19  Updated: 07/Jul/20  Resolved: 25/Sep/19

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

Type: Task Priority: Neutral
Reporter: Mikaël Geljić Assignee: Federico Grilli
Resolution: Done Votes: 0
Labels: ui-tests, ui-tests-framework
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLTEST-49 Enable running of JUnit5 and JUnit4 U... Closed
supersession
supersedes MGNLTEST-53 Start productizing page object initia... Closed
is superseded by MGNLTEST-51 Complete phase 1 of new page object b... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: core-TF-features-bugs-improvements
Story Points: 3

 Description   

Scope:

  • Provide "self-tests" to catch reliability issues on API level, instead of usage level
  • Focus on high-order POs such as ContentApp, Form, FindBar, etc.
    • ideally one test-class for each PO, testing each's public contract (so we can add more tests stressing reliability a bit too)


 Comments   
Comment by Christoph Meier [ 04/Sep/19 ]

Please create a new package for the "self-tests" (to have a clear distinctin between the self-tests and the "real" functional tests.

Proposed package: info.magnolia.testframework.selftests

Existing classes to be moved to that package:

  • info.magnolia.functionaltests.ContentAppFunctionalTest
  • info.magnolia.functionaltests.PagesAppFunctionalTest
  • info.magnolia.functionaltests.SecurityAppFunctionalTest
  • info.magnolia.testframework.UserMenuSelfTest
  • info.magnolia.testframework.SeleniumSelfTest
Generated at Mon Feb 12 07:45:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.