All imho. That kind of CI testing is for 389 so feel free to implement it how you prefer. >from lib389._constants import DN_DM "_constants" is private. Import directly from lib389 ;) For testing purposes, we could create harnesses for setup/remove new instances. For test names: m1c1_test.py # a novice won't understand Peace, R On Wednesday 30 October 2013 17:47:44 thierry bordaz wrote: > Hello, > > This tickets implement a test case and propose a layout of the CI > tests in the 389-ds. > The basic idea is to put CI tests under: > <head>/dirsrvtests/ > tickets/ > standalone_test.py > m1c1_test.py > m2_c1_test.py > ... > > testsuites/ > acl_test.py > replication_test.py > ... > > For example, test_standalone.py would setup a standalone topology > and will contain all ticket test cases that are applicable on > standalone topology. > > https://fedorahosted.org/389/attachment/ticket/47575/0001-Ticket-47575-CI-te > st-add-test-case-for-ticket47560.patch > > regards > thierry -- Roberto Polli Community Manager Babel S.r.l. - http://www.babel.it T: +39.06.9826.9651 M: +39.340.652.2736 F: +39.06.9826.9680 P.zza S.Benedetto da Norcia, 33 - 00040 Pomezia (Roma) CONFIDENZIALE: Questo messaggio ed i suoi allegati sono di carattere confidenziale per i destinatari in indirizzo. E' vietato l'inoltro non autorizzato a destinatari diversi da quelli indicati nel messaggio originale. Se ricevuto per errore, l'uso del contenuto e' proibito; si prega di comunicarlo al mittente e cancellarlo immediatamente. -- 389-devel mailing list 389-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-devel
