[Owncloud] Making internal methods public for unit testing

[Sam Tuke]

OCP\User currently provides access to user-related methods commonly used by 
apps. For unit testing however, access to more methods are required, such as 
useBackend(), in order to make use of the dummy OC_User_Dummy user management 
backend.

I imagine that other methods will also require access via a public interface 
for unit testing other functionality (not just relating to user.php).

Therefore, although I can provide access to unit tests by simply adding 
wrappers for methods like useBackend() to OCP\User, I wonder whether there is 
a better option which doesn't result in a slew of new wrappers duplicating 
input and output?

Best,

Sam.
-- 
Sam Tuke
British Team Coordinator
Free Software Foundation Europe
IM : samtuke at jabber.fsfe.org
Latest UK Free Software news: uk.fsfe.org
Is freedom important to you? Join the fellowship.fsfe.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/owncloud/attachments/20120601/1c5d4659/attachment.sig>