@Test
    public void testMethodMapping() {
        mapper = getMapper("mappings/testDozerBeanMapping.xml");
        MethodFieldTestObject sourceObj = newInstance(MethodFieldTestObject.class);
        sourceObj.setIntegerStr("1500");
        sourceObj.setPriceItem("3500");
        sourceObj.setFieldOne("fieldOne");
        MethodFieldTestObject2 result = mapper.map(sourceObj, MethodFieldTestObject2.class);
        assertEquals("invalid result object size", 1, result.getIntegerList().size());
        assertEquals("invalid result object value", 3500, result.getTotalPrice());
        assertEquals("invalid result object value", "fieldOne", result.getFieldOne());
        // map back
        MethodFieldTestObject result2 = mapper.map(result, MethodFieldTestObject.class);
        // if no exceptions we thrown we are good. stopOnErrors = true. both values will be null
        // since this is a one-way mapping we shouldn't have a value
        assertNull(result2.getFieldOne());
    }
When the source type is a Set and the destination is a Collection we expect that the
mapper narrows to the Set type instead of using a List by default.
<p>
issue https://github.com/DozerMapper/dozer/issues/287
core/src/test/java/com/github/dozermapper/core/functional_tests/GranularDozerBeanMapperTest.java