By Vlad Marian vmarian@mimecast.com
The primary usage is done via JSON files called test cases. Cases are client configuration files ran as Junit tests.
This project can be compiled into a runnable JAR. A CLI interface is implemented with support for both client and server execution.
Mimecast uses this to run smoke tests every time a new MTA snapshot is built. This helps identify bugs early before leaving the development environment.
Contributions of any kind (bug fixes, new features...) are welcome! This is a development tool and as such it may not be perfect and may be lacking in some areas.
Certain future functionalities are marked with TODO comments throughout the code. This however does not mean they will be given priority or ever be done.
Any merge request made should align to existing coding style and naming convention. Before submitting a merge request please run a comprehensive code quality analysis (IntelliJ, SonarQube).
Read more here.
This project makes use of sample password as needed for testing and demonstration purposes.
- notMyPassword - It's not my password. It can't be as password length and complexity not met.
- 1234 - Sample used in some unit tests.
- giveHerTheRing - Another sample used in unit tests and documentation. (Tony Stark / Pepper Pots easter egg)
- avengers - Test keystore password that contains a single entry issued to Tony Stark. (Another easter egg)
These passwords are not in use within Mimecast production environments.