[389-devel] Running lib389 tests

[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 test fails it
> doesn't run the teardown function.
>
>> I do not understand how you can test 'list' if you have not
>> 'create' mapping_tree before.
> I would have created the list_test requirements in the setup phase.
>   (in the link below I created two different backends for two different test
> cases)
> https://github.com/ioggstream/dsadmin/blob/merge_lib389/tests/replica_test.py#L54
>
>
> While I started with dependent tests on dsadmin, I spent some time to change
> that approach because small changes caused whole testsuites to fail and it was
> difficult to find where the error was (in the setup? in the test first code?
> in the second test code? in the library code? )

Ok I agree
>
> Peace,
> R.
>