Associating a clean .kdevduchain repo for unit tests

David Nolden david.nolden.kdevelop at art-master.de
Mon Aug 31 11:25:09 UTC 2009


Am Montag 31 August 2009 13:19:22 schrieb 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?
Yes, it's not yet implemented.





More information about the KDevelop-devel mailing list