On Tue, Jul 3, 2012 at 3:02 PM, Dario Freddi <[email protected]> wrote:
> Hey, > > 2012/7/1 Vishesh Handa <[email protected]>: > > Hey Sebastian > > > > 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. > > if you need any help with the DBus magic, I've gone through that with > autotests in ktp-testlib and tp-qt, so feel free to shoot me a mail > Thanks. Right now everything is working really well. But I will bug you if something crops up. > > > > > 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? > > > > [1] http://vhanda.in/blog/2012/03/nepomuk-test-framework/ > > -- > > Vishesh Handa > > > > > > _______________________________________________ > > 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
