Test coverage for ml gradle

If you look in the test source directory, you won't see much in the way of tests for ml-gradle. Why is that???

Two answers - first, most of what ml-gradle does is handled by the ml-app-deployer library, which has extensive JUnit-based tests for its functionality. Generally, when a new feature is added to ml-gradle, almost all of it is implemented in ml-app-deployer, and then a little tweak will be made to ml-gradle, or nothing at all will be done to ml-gradle.

Second, the small amount of logic - largely defining tasks and collecting inputs to pass to a class defined by ml-app-deployer - in ml-gradle simply hasn't proven to be a significant source of bugs. Thus, manual testing of changes made to ml-gradle has proven to be sufficient in terms of the time/money spent. Conversely, manual testing of changes to ml-app-deployer would require significant amounts of time and likely be very risky, as manual testing rarely can cover the variety of scenarios that proper automated tests can.

Ideally, ml-gradle would have a set of automated tests to cover the things that it does, but this has not proven to be a priority yet. However, automated test coverage in ml-app-deployer will continue to be of the highest priority possible for any changes made to that library.