Re: [389-devel] Running lib389 tests

2014-01-24 Thread thierry bordaz
On 01/24/2014 03:50 PM, Roberto Polli wrote: Hi T, On Thursday 23 January 2014 14:19:52 thierry bordaz wrote: In a day to day work, I prefer to run an individual test under eclipse so that I can isolate the tests. I recommend you look at

Re: [389-devel] Running lib389 tests

2014-01-24 Thread Roberto Polli
On Friday 24 January 2014 15:56:10 thierry bordaz wrote: Do we really need to get rid of __main__ when using nose/py.test ? Obviously you can take it. I would just avoid noise in testing. Moreover they could leave your environment dirty: eg. if a test fails it doesn't run the teardown

Re: [389-devel] Running lib389 tests

2014-01-24 Thread thierry bordaz
On 01/24/2014 04:18 PM, Roberto Polli wrote: On Friday 24 January 2014 15:56:10 thierry bordaz wrote: Do we really need to get rid of __main__ when using nose/py.test ? Obviously you can take it. I would just avoid noise in testing. Moreover they could leave your environment dirty: eg. if a

[389-devel] Running lib389 tests

2014-01-23 Thread Roberto Polli
Hi Thierry + @all, I'd like to play with the new lib389 and try to split DirSrv in two layers: - the old approach DSAdmin for TCP communication - DirSrv implementing your interface essentially I would put class DirSrv(DSAdmin): # ...new stuff go here ... class DSAdmin(SimpleLDAPObject):

Re: [389-devel] Running lib389 tests

2014-01-23 Thread thierry bordaz
On 01/23/2014 12:42 PM, Roberto Polli wrote: Hi Thierry + @all, I'd like to play with the new lib389 and try to split DirSrv in two layers: - the old approach DSAdmin for TCP communication - DirSrv implementing your interface essentially I would put class DirSrv(DSAdmin): # ...new