Automated tests using dovecot
Nicolas Sebrecht
nicolas.s-dev at laposte.net
Sat Jun 11 12:06:54 BST 2011
On Thu, Jun 09, 2011 at 08:37:55PM +0200, Nicolas Sebrecht wrote:
> To do so, I propose to use these paths:
>
> /test/ # root test directory
> |
> |
> `tests-suites.conf # where testers configure the environment(s) they like
> |
> `update-tests-suites.sh # fetch choosen environment, configuration
> | # sample files from an external repository
> |
> `start-tests.sh
> |
> `scenarios # our scenarios for OfflineIMAP
> |
> `imap-server/ # where to store external repositories and
> | # high-level API scripts for cooking
> |
> `system-wide/
> | |
> | `dovecot-vXYZ/ # configuration file samples, low-level
> | | # scripts for cooking, etc
> | |
> | `imapserver2-vXYZ/
> |
> `environments
> |
> `dovecot-vXYZ/ # dovecot chrooted environment, low-level
> | # scripts for cooking, etc
> |
> `imapserver2-vXYZ/
Thinking about that again, I think the whole /test directory should be a
dedicated git repository. The reason is that it would let people test
older OfflineIMAP releases with latest scenarios.
So, we should have a /update-test-suites.sh script outside of /test.
--
Nicolas Sebrecht
More information about the OfflineIMAP-project
mailing list