Re: [389-devel] Please review lib389 ticket 47578: removal of 'sudo' and absolute path in lib389

On 10/30/2013 07:56 PM, Jan Rusnacko wrote: Hi Jan, thanks for you comments. py.test will call for for each test_ticketxxx setup test_ticketxxx teardown setup will create the instance if it does not already exist, else it provide a dirsrv to it. teardown will remove the instance if the test_ticketxx is not able to properly clean it up (if test_ticketxx raise the clean_please flag) test_ticketxxx will start it executions with clean_please=true (set by setup), if it succeeds it set clean_please=false. Unless it fails to properly clean up the instance. In that case it sets clean_please to true. What would be the advantages to make the setup/teardown sub-methods of the test_ticketxx ? At least a "small" drawback is that the person that write test_ticketxxx will have to write them, instead of using the "standard" one. Right, it was my first intention. But then I had this idea to group the tickets per deployment module. I don't know if it is a good idea, but it seems to be confusing :-[