Create unit tests for the main engine, and each of the built-in tasks, as well as for the CLI.
Integrate with https://travis-ci.org/
A lot has been done for this issue. Automaton already has a lot of important tests, but we still need to complete it. Also, Travis CI has already been integrated.
@filipediasferreira all the tasks are implemented, including cp and mv.
chmod, cp, mkdir, mv, rm and symlink are supposed to work just like they work in unix, except that we can specify multiple entries. For instance:
'my/path/to/src': 'my/path/to/dst', // Equivalent to mv my/path/to/src my/path/to/dst
'my/path/to/src2/*': 'my/path/to/dst2/' // Equivalent to mv my/path/to/src2/* my/path/to/dst2/
Please note that the cp and mv tasks have various combinations of source/destination that can change the outcome.
For instance, adding a trailing slash to the destination has a different behavior in some cases.
Please experiment a bit in your terminal and you will see what I mean. The more complete these particular tasks tests, the better.
I would also like to request to actually give priority to cp and mv, because they probably aren't conforming 100% with the unix implementation. Please look at the TODO's written in the cp and mv tasks to see what I mean.
Core tests are done.
Going to work on the CLI tests tomorrow.
Logging + rudimentary CLI tests are done.
@filipediasferreira don't forget to finish up the mv tests
I will take care of this on the next few days ;)
Added mv task unit tests #12
Thanks @filipediasferreira, going to close this out! We got plenty of tests.