Config Editor: Unit Test Coverage EditorParameterPersistence Servlet
test coverage for EditorParameterPersistence is corrently too low.
in the latest release of aem/sling-mock 1.1 a good support for testing servlets with request/response mocking was added, this should make it easy.
thanks, two last remarks on this class:
you can remove the method sanityCheck - if the mandatory osgi references cannot be set, the servlet will not be started at all - the code is not reachable
please provide a unit test for the code path around getLockedParameterNames as well
I have refactored the test for EditorParameterPersistence to use aem/sling mocks. currently testing the right values conversion from the request parameters to persistence data, by capturing the argument of the parameterPersistence service.