Associating a clean .kdevduchain repo for unit tests

[Milian Wolff]

David Nolden, 31.08.2009:
> Am Mittwoch 26 August 2009 12:41:36 schrieb Milian Wolff:
> > PHP has the problem that it requires a clean .kdevduchain for unit
> > tests. And I'd say it would make sense for other languages as well to
> > always operate on a clean .kdevduchain repo in unit tests.
> >
> > Is there any way we can enfore a kdevduchain repo for unit tests? Giving
> > it a name like the INT_MAX value or something would make it _very_
> > unlikely that it ever gets an existing repo.
> >
> > Oh and before I forget it: Unit tests can disable _writing_ to a repo
> > (very good!), but not disable _reading_ from a repo.
> > See:
> >      DUChain::self()->disablePersistentStorage();
>
> Maybe the simplest and cleanest solution would be also disabling the
> _loading_ of a repository when persistent storage is disabled.

But that is currently not implemented, right?
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090831/c39552f2/attachment.sig>