> Should adapters or wrappers be unit tested
yes the main responsibility of the wrapper should be unit tested through the wrapper
no not the complete functionality should be unit tested through the wrapper
Here is an example that illustrates what i mean:
if you have a
MyComplicatedBusinessCalculationWebservice that combines calculation and permissions
you should have full unittests for calculation and full unittests for permissions.
For the webservice you should only have to test that for every webservice method the corresponding calculation is called and that permissioncheck is applied.
There is no need to test through webservice the combinations of permissions are correct since you already have tested these with the permission-unittests.
There is no need to test through webservice the different edgecases for businesscalculations since you already have tested these with the calculation-unittests.
I would not recomment to test the underlying classes through the webservice.
If MyPermissionManager changes only the MyPermissionManager-Unittests must be updated but not the webservice-tests