Split into reusable, isolated modules #1369

Problem or motivation

Currently framework source code is logically grouped into modules but there are no clear boundaries and so there are few problems.

• it's not possible to use annotations only in other project
• it's not possible to use reporters core in other projects
• it's not possible to use expectations in other projects

Proposed solution

The goal of this work is to split the framework into sub-modules with clear boundaries and one-way dependencies.

Having standalone modules will make it easier to create another framework like cucumber for PLSQL that would be based on the same core elements with different structure (suite), different runner and different reports.

Alternatives or workarounds considered

Of course new frameworks could be built into existing framework as a whole, without splitting it into modules but it would create a monolith that will be even harder to maintain in future and it will make even harder to introduce new changes to the framework in future.

Framework area

Other