[MAGNOLIA-7503] Make a better alternative for RepositoryTestCase testing use cases Created: 10/Apr/19  Updated: 07/Jul/20  Resolved: 07/Jul/20

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

Type: Improvement Priority: Minor
Reporter: Andres Garcia Assignee: Andres Garcia
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

RepositoryTestCase is a largely used class with many responsabilities within, as well as being an abstract class it introduces rigidness in the testing classes that might need it (since said test classes cannot inherit from others, as, for example, when using contract tests inheritance).

RepositoryTestCase might be deprecated (not removed) in favor of the better way of testing this scenarios (JUnit Rule/Extension/Runner for example). Some tests might be migrated. Also consider its parent class for refactor.


Generated at Mon Feb 12 04:24:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.