There are some entities like Subscription and Offering that are owned by the Swatch Tally service. This means that any changes and migrations will be done in Swatch Tally.

The problem is that the Swatch Contract service also uses some of these entities and we need to be sure that these same entities from Swatch Contract and Swatch Tally are in sync. Otherwise, issues like SWATCH-1879 will continue happening.

Possible solutions are:

• Declare the shared entities in a common module.
• Or somehow apply the migration steps from swatch tally when running the swatch contracts tests (and not use mocks for the entity repositories).

Acceptance Criteria

• For the contracts and subscriptions, these two entities could be refactored into only one entity that should be placed in a common module.
• Swatch Contracts tests should not use mocks for the repository (at least, for the offering and subscription entities).
• Swatch Contracts should create the offering and subscription entities using the migration files from Swatch tally before running the tests.