On Mon, Jul 2, 2012 at 3:40 PM, Mario Fux <[email protected]> wrote:
> Am Sonntag 01 Juli 2012, 15.05:39 schrieb Vishesh Handa: > > Hey Sebastian > > Morning > Morning > > > I've been working on a major refactoring on the Nepomuk::Resource code > > base, and I realized that I was adding bugs, so I started working on unit > > tests so that I could easily fix them. Unfortunately, unit testing is > kinda > > hard cause of the entire dbus architecture. This is where my test > suite[1] > > comes into play. > > > > I've sketched out a rough plan of all the unit tests that we need to test > > all the code paths, and I've implemented some of them and discovered a > > number of bugs already (with the original implementation). My problem is > > that where should those tests be committed? > > > > Right now it's there in a local repo. I could push them into the test > > framework, but that's also in a scatch repo. > > > > Should I move my 'nepomuk-testlib' to the playground/kdebase or should I > > just add that code into nepomuk-core? That way we can have the tests in > the > > same code base. > > > > Any ideas? > > I'm not Sebastian but this could help you: > > http://community.kde.org/Frameworks/Strategy_and_Policies#Frameworks_have_automatic_unit_tests > > It's about the directory structures of the future KDE Frameworks. > Ah. So according to this the tests should be in a folder called autotests Plus, I think it makes more sense to have the tests in the same repository as the code it is testing. So I'm maybe going to move the test suite to nepomuk-core. > > [1] http://vhanda.in/blog/2012/03/nepomuk-test-framework/ > > thx > Mario > _______________________________________________ > Nepomuk mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/nepomuk > -- Vishesh Handa
_______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
