Current version of test-fwk (1.3.x)

• has a big library of POs for AdminCentral UIs. PO implementations are using Selenium API. Not using Selenide.
• cannot yet trigger UI-tests via cucumber

Various sub-modules in SaaS run UI tests

• with custom POs based on Selenide - but they are scattered - likely with some code-duplications
• many (all?) of the UI tests are using cucumber (where tests are triggered differently), though cucumber tests utilize junit "vintage" fwk
•  

Next level test-fwk

• Is able to trigger UI-tests the cucumber-way using Selenide POs
  • Not using JUnit-vintage-fwk to run/pick-up cucumber - instead using latest libs from cucumber & JUnit
• Provides a set of POs for non-AdminCentral-UIs used in SaaS-UI-tests. Those POs likely will utilize Selenide
• still can run our existing POs which are not using Selenide

Initially we had no plan of replacing / refactoring existing POs (for AdminCentral).
Now we have changed our opinion about this . As for now foundation considers to rewrite most it not all of the POs using Selenide - See MGNLTEST-281

The test-fwk should be able to utilize both types of POs - those we have which are not using Selenide, plus new ones which use Selenide.