Details
-
Improvement
-
Resolution: Outdated
-
Neutral
-
None
-
4.4.4
-
None
Description
Customer use case
I've recently been developing a service that uses Magnolia as the underlying content store. I have a small API that is exposed as a REST service that allows me to retrieve certain pieces of content programatically in my application.
As part of the development process, I wanted to test my service against a "real" Magnolia instance not just using Mock objects. This is to ensure that I am using the Magnolia API correctly. I wanted this to be something that I could run as a unit test to make the process of testing and fixing bugs efficient.
Problem
There are a number of test utilities that make this possible. In particular I have made good use of info.magnolia.test.RepositoryTestCase. There are also a number of other utilities that have been developed to solve problems associated with writing this type of unit test. In my case, info.magnolia.module.templatingkit.util.SureFireModuleManager helps to work around a known problem with classloading when using the Maven Surefire plugin to run my unit tests.
The problem is that these utilities are scattered throughout different projects. It makes them hard to locate, and it also makes the dependencies for my tests overly complicated.
Suggestion
Consolidate all of the various testing utilities into a single test framework, making it easier for customers to test their applications against a "real" Magnolia instance from unit tests.