Why fork? Consider making PR's against the original

[tedivm]

I'm always a fan of pull requests and love the improvements you've made to this project.

[frankrousseau]

@aenario I let you answer to the question.

[aenario]

Hi @tedivm,

There is basically 2 big changes in this fork

1 - Javascript It was mostly because I didn't know bash, so it was easier to convert SetupEnvironement.sh to JS in order to make the changes I needed. I think this should not be merged back, because it's cool one can use DovecotTesting with any language. Eventually, we could add a package.json and a JS wrapper of the CLI, because for node developper, its more convenient to have everything in NPM, but that's more of a nice to have.

2 - Some enhancements

• apply the "travis" process if one is already in a vagrantbox USER='vagrant' --> Should be ported easily
• easy way to get the server IP, depending of the above --> Not sure how to make this in bash, an separate get-ip.sh file or an option of SetupEnvironment.sh ?
• wait for dovecot to start --> Idem, plus I am not sure how to wait for the server to accept connection in bash
• script to change UIDValidity of the Sent box --> Easy to contribute, need a way to call it from outside the vagrant or not. Problably another changeuidvalidity.sh at the root of the project
• the forcedcleanstate which rm -rf everything before setup environment. --> I dont remember when it was a problem ...
• The import process (which use nodejs a lot and is a PITA to use) --> Would be better to make it again in bash, not sure how to do that though. Could be contributed as part of the javascript packaging.

Let me know which parts interest you and how you'd like them done and I will take a look sometime next week.

Thanks again for your initial work, it was really really a life savior when we made the test suite.