[prev in list] [next in list] [prev in thread] [next in thread] 

List:       owncloud
Subject:    Re: [Owncloud] Making internal methods public for unit testing
From:       Sam Tuke <samtuke () owncloud ! com>
Date:       2012-06-12 17:24:27
Message-ID: 1359250.Z8iFZSgJQX () sam-desktop
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday 04 June 2012 12:53:02 Frank Karlitschek wrote:
> > What are you testing, if it is the core, why not use the core OC_ classes?

I'm testing the files_versions app. In order to test any functionality that 
interacts with users, a dummy backend for the User class must be loaded.

> Same question from me. I donīt think we should make our public API bigger
> than needed only because we want to use unit tests.

If we want apps to have unit tests, then any part of OC which must be accessed 
for the writing of tests should be in the public namespace. It seems to me 
that OCP\User class is just as public as any other class that needs access for 
the testing of an app.

Best,

Sam.
["signature.asc" (application/pgp-signature)]

_______________________________________________
Owncloud mailing list
Owncloud@kde.org
https://mail.kde.org/mailman/listinfo/owncloud


[prev in list] [next in list] [prev in thread] [next in thread]