[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kolab-devel
Subject:    Re: [Kolab-devel] Hello Kolab Devs
From:       James Mills <prologic () shortcircuit ! net ! au>
Date:       2013-09-09 23:22:36
Message-ID: CALGqR9KC4zSPO=Q3-u_kTK57t2WHZ5x=OspPp1q+xhDKNMLpPg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Tue, Sep 10, 2013 at 5:03 AM, Jeroen van Meeuwen (Kolab Systems) <
vanmeeuwen@kolabsys.com> wrote:

> sorry to get back to your introduction email so late - meanwhile we've
> spoken on IRC a lot ;-)
>

That's alright :)

I've started creating (nose) test-cases for pykolab, that is probably the
> way we want to move forward. The tests are split in two parts (unit and
> functional). For a series of functional tests one has to have set up a
> Kolab system beforehand, for which I recommend using domain "example.org"
> and root dn "dc=example,dc=org" - and all passwords set to
> "Welcome2KolabSystems" - this enables the use of kolab-scripts[1] as well,
> without modifications.
>

Are you opposed to using py.test (1) at all? I find it less cumbersome and
less boilerplate for writing unit and system tests. In my own project
(circuits) I tried the std. lib unittest as well as nose before discovering
py.test afterwhich I ended up writing hundreds of tests (because it's so
easy and straightforward!).

cheers
James

1. http://pytest.org/latest/

[Attachment #5 (text/html)]

<div dir="ltr">On Tue, Sep 10, 2013 at 5:03 AM, Jeroen van Meeuwen (Kolab Systems) \
<span dir="ltr">&lt;<a href="mailto:vanmeeuwen@kolabsys.com" \
target="_blank">vanmeeuwen@kolabsys.com</a>&gt;</span> wrote:<div \
class="gmail_extra">

<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">sorry \
to get back to your introduction email so late - meanwhile we&#39;ve spoken on IRC a \
lot ;-)<br>

</blockquote><div><br></div><div>That&#39;s alright :)  \
</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">


I&#39;ve started creating (nose) test-cases for pykolab, that is probably the way we \
want to move forward. The tests are split in two parts (unit and functional). For a \
series of functional tests one has to have set up a Kolab system beforehand, for \
which I recommend using domain &quot;<a href="http://example.org" \
target="_blank">example.org</a>&quot; and root dn &quot;dc=example,dc=org&quot; - and \
all passwords set to &quot;Welcome2KolabSystems&quot; - this enables the use of \
kolab-scripts[1] as well, without modifications.<br>

</blockquote><div><br></div><div>Are you opposed to using py.test (1) at all? I find \
it less cumbersome and less boilerplate for writing unit and system tests. In my own \
project (circuits) I tried the std. lib unittest as well as nose before discovering \
py.test afterwhich I ended up writing hundreds of tests (because it&#39;s so easy and \
straightforward!).  </div>

<div><br></div><div>cheers</div><div>James</div><div><br></div><div>1.  <a \
href="http://pytest.org/latest/">http://pytest.org/latest/</a></div></div></div></div>




_______________________________________________
devel mailing list
devel@lists.kolab.org
https://lists.kolab.org/mailman/listinfo/devel

[prev in list] [next in list] [prev in thread] [next in thread]