Re: [Kolab-devel] Hello Kolab Devs
James Mills <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Message-ID | <CALGqR9+z4u5f7JwgooRpeOexBT1BSXQGZoC-0iJM29JA-RR9Xg__46088.7241097682$1378808066$gmane$org@mail.gmail.com> |
On Tue, Sep 10, 2013 at 6:31 PM, Jeroen van Meeuwen (Kolab Systems) < [email protected]> wrote: > ave no objections, but could you show me before we change all of what we >> have already? ;-) > > Cool :) Hold off on any new ones. I'll try to port some existing ones to py.test and you'll see how much simpler it is :) > Question on the side... does py.test keep stdin/stdout/stderr open? I've > been trying to get std. unittest to do this for me, so that I can do: > > 0) Clean out environment completely, > > 1) Set the environment up for a functional test of application $x, > > 2) Display the steps to reproduce and ask the Quality Assurance engineer > for confirmation, > > 3) Handle the ACK / NAY response. Yes yes yes and yes. py.test has lots of cool stuff :) I'll try to borrow from my vast experience with circuits's unit tests and system tests :) cheers James _______________________________________________ devel mailing list [email protected] https://lists.kolab.org/mailman/listinfo/devel