morto | Superseded by Circle CI 2.0 and Makefiles

Morto organises projects by subdirectory. It currently assumes that each subdirectory is its own project, and that there are no dependencies between projects. You can put system integration tests in subdirectories too, but those are not projects. If a system integration test changes, Morto will run all the tests.
Each project can either have a subDirectory (in which case it will only setup/test that project in CI if files in that directory have changed) or alwaysRun.
Each project needs to have a number of setupCommands, split between common (run regardless of platform), osx (run only when you don't use the --ci flag) or ci (run only when you use the --ci flag).
A project can either have testRunners (simply runs the commands) or fileTestRunner (will use this command when passing in a file, e.g. morto test core/file_spec.rb would run something like cd core && bundle exec rspec file_spec.rb).
You can specify a junitOutput, which we will collect in one output if you use the --junitOutput flag.
Morto is currently pretty tied to CircleCI and Github. Our circle.yml looks something like this:.