You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2009/11/05 00:57:32 UTC

[jira] Resolved: (SLING-1166) Provide helper class for simpler unit testing of sling code

     [ https://issues.apache.org/jira/browse/SLING-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz resolved SLING-1166.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: Commons Testing 2.0.6
         Assignee: Bertrand Delacretaz

Patch applied in revision 832916, thanks!

> Provide helper class for simpler unit testing of sling code
> -----------------------------------------------------------
>
>                 Key: SLING-1166
>                 URL: https://issues.apache.org/jira/browse/SLING-1166
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>            Reporter: Alexander Klimetschek
>            Assignee: Bertrand Delacretaz
>             Fix For: Commons Testing 2.0.6
>
>         Attachments: SLING-1166.patch
>
>
> When writing unit tests that do a bit of integration in Sling, you often need the following:
> - a JCR repository
> - registered node types
> - a JCR-based resource resolver
> - adapter managers (to support all the adaptTo methods in your code)
> This covers most of what has to be done to run unit tests for services without an OSGi container running. I have written such a helper class for our product and would like to contribute it to Sling, especially to write unit tests for SLING-1131. Patch will follow.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.