[SLING-7978] Sling Mocks: Allow easy access to the ModelFactory

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: Site, Testing
• Assignee: Unassigned
• Reporter: Konrad Windszus
• Created: 04/Oct/18 15:54
• Updated: 05/Oct/18 10:27
• Resolved: 05/Oct/18 10:27

Description

Currently you would instantiate a Sling Model in a unit test leveraging Sling Mocks via

@Rule
  public SlingContext context = new SlingContext(ResourceResolverType.RESOURCERESOLVER_MOCK);

 @Test
  public void testModel() {
    context.load()
           .json(<some json resource from the classpath>, "/page1");
    context.addModelsForClasses(MyModel.class);

    MyModel model = context.resourceResolver().getResource("/page1").adaptTo(MyModel.class)

  // model is now null for some reason, hard to debug why

In case for some reason the model cannot be instantiated it is hard to debug why (because by default the reason is only emitted in the log with level DEBUG). To ease debugging it would be nice if ModelFactory (SLING-3709) could be used, as that throws an explicit exception in case of instantiation errrors. It would be nice to give direct access to that service directly from the SlingContext.
 

Issue Links

• relates to: SLING-3709 Sling Models: Allow caller to deal with exceptions
• links to: GitHub Pull Request #24