[ https://issues.apache.org/jira/browse/SLING-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567107#comment-14567107 ]
Bertrand Delacretaz commented on SLING-4757: -------------------------------------------- I have committed your unit tests in revision 1682844, thanks! With minor changes in revision 1682845. Made a small change to FileNameExtractorImpl in revision 1682850, that allows checking the (unlikely) UnsupportedEncodingException. I said earlier that we want to minimize changes to the main code, but in this case it makes it more testable without impact on its functionality, so I think it's a valid exception. I'll look at the integration tests later, hopefully today in 3-4 hours. > Improve test coverage and add integration tests to the contentdetection module > ------------------------------------------------------------------------------ > > Key: SLING-4757 > URL: https://issues.apache.org/jira/browse/SLING-4757 > Project: Sling > Issue Type: Improvement > Components: Commons > Reporter: Bertrand Delacretaz > Assignee: Petr Shypila > Attachments: > FileNameExtractorImpl_Injection_failed__ClassNotFoundException.patch, > week2-part1-unit-tests.patch, week2-part2-integration-tests.patch > > > The new SLING-4694 contentdetection module has reasonable test coverage but > there are some gaps, and it's also missing some integration tests to verify > that the services provided by the bundle are correctly made available in an > OSGI environment. > I'll take this opportunity to ask our GSoC student [~petr.shypila] to expand > these tests, as that's a good example of what we're trying to do with his > tests improvement project. > So [~petr.shypila] here's your "mission" ;-) > Buliding bundles/commons/contentdetection with with -Pjacoco-report and > looking at target/site/jacoco/index.html shows that a few things are not > tested. The first step is to add the missing unit tests to improve that, > maybe provide a first patch with just that. > Then, we'd like to add integration tests that start this bundle in an OSGi > environment and verify that the ContentAwareMimeTypeService and > FileNameExtractor services are available and work. No need to duplicate the > unit tests, just verify that the services are here and work in a simple case. > The best way to do this is probably with Pax Exam, the > ResourceBundleProviderIT. is a good example of that and there are other > examples in our codebase if you search for *IT.java files that contain > "pax.exam". > As usual, try to minimize changes to the pom (except for what's directly > related to testing) and to non-test code. > Feel free to ask if you have any questions of course, either here for minor > ones or on the dev list for larger discussions. > [1] > https://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/i18n/src/test/java/org/apache/sling/i18n/it/ResourceBundleProviderIT.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)