[prev in list] [next in list] [prev in thread] [next in thread]
List: nepomuk
Subject: Re: [Nepomuk] Nepomuk Test Library
From: Vishesh Handa <me () vhanda ! in>
Date: 2012-07-02 11:08:15
Message-ID: CAOPTMKBHWc0SbWn2Z2DpPb9WmKvNNGfaqUaXMOk7hcBHpwY2GQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Mon, Jul 2, 2012 at 3:40 PM, Mario Fux <kde-ml@unormal.org> 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
> Nepomuk@kde.org
> https://mail.kde.org/mailman/listinfo/nepomuk
>
--
Vishesh Handa
[Attachment #5 (text/html)]
<br><br><div class="gmail_quote">On Mon, Jul 2, 2012 at 3:40 PM, Mario Fux <span \
dir="ltr"><<a href="mailto:kde-ml@unormal.org" \
target="_blank">kde-ml@unormal.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> Am Sonntag 01 Juli 2012, 15.05:39 schrieb Vishesh Handa:<br>
> Hey Sebastian<br>
<br>
Morning<br></blockquote><div><br>Morning<br> <br></div><blockquote \
class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> <div><div class="h5"><br>
> I've been working on a major refactoring on the Nepomuk::Resource code<br>
> base, and I realized that I was adding bugs, so I started working on unit<br>
> tests so that I could easily fix them. Unfortunately, unit testing is kinda<br>
> hard cause of the entire dbus architecture. This is where my test suite[1]<br>
> comes into play.<br>
><br>
> I've sketched out a rough plan of all the unit tests that we need to \
test<br> > all the code paths, and I've implemented some of them and \
discovered a<br> > number of bugs already (with the original implementation). My \
problem is<br> > that where should those tests be committed?<br>
><br>
> Right now it's there in a local repo. I could push them into the test<br>
> framework, but that's also in a scatch repo.<br>
><br>
> Should I move my 'nepomuk-testlib' to the playground/kdebase or should \
I<br> > just add that code into nepomuk-core? That way we can have the tests in \
the<br> > same code base.<br>
><br>
> Any ideas?<br>
<br>
</div></div>I'm not Sebastian but this could help you:<br>
<a href="http://community.kde.org/Frameworks/Strategy_and_Policies#Frameworks_have_automatic_unit_tests" \
target="_blank">http://community.kde.org/Frameworks/Strategy_and_Policies#Frameworks_have_automatic_unit_tests</a><br>
<br>
It's about the directory structures of the future KDE \
Frameworks.<br></blockquote><div><br>Ah. So according to this the tests should be in \
a folder called autotests<br><br>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.<br> <br></div><blockquote class="gmail_quote" \
style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> <br>
> [1] <a href="http://vhanda.in/blog/2012/03/nepomuk-test-framework/" \
target="_blank">http://vhanda.in/blog/2012/03/nepomuk-test-framework/</a><br> <br>
thx<br>
Mario<br>
_______________________________________________<br>
Nepomuk mailing list<br>
<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/nepomuk" \
target="_blank">https://mail.kde.org/mailman/listinfo/nepomuk</a><br> \
</blockquote></div><br><br clear="all"><br>-- <br><span \
style="color:rgb(192,192,192)">Vishesh Handa</span><br><br>
_______________________________________________
Nepomuk mailing list
Nepomuk@kde.org
https://mail.kde.org/mailman/listinfo/nepomuk
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic