| Valid point. I started this about a month ago, and as APIs were evolving I did not want to slow my velocity by having the tests fight against shifting it around. I suspect the first release will be in about Feburary, but the time to collaborate on working on it is now. It is designed to be fairly testable, but if you've ever written a similar system, you know that distributed testing of modules on a matrix of 12 platforms IS a trainwreck. Any units would mostly be proving out the language. The best way to do that is with a specialized callback, that shares the event stack, and we can then introspect that the events happened in the correct order. As the callbacks have been changing too much now, writing a boatloat of tests would have been a mistake. At this point, I'm most interested in feedback on language features, and these will come. It was an absolute mistake that ansible itself was not more testable at a mock level, a problem made a lot better now by everything being done in one process. Ansible had the ability to write modules in any language, but this was never really used in practice. |