There is a benefit between testing segway-task dry runs of Segway (without running the task itself). Tests would be significantly lighter weight and would allow unit testing on individual code bases if necessary. Faster and smaller tests would make adding future tests, functionality, or making changes a lot easier to manage and verify that everything works as intended.
It might be best to also keep a test like the current "data" test as-is for a full run.
Original report (BitBucket issue) by Eric Roberts (Bitbucket: ericr86, GitHub: ericr86).
There is a benefit between testing segway-task dry runs of Segway (without running the task itself). Tests would be significantly lighter weight and would allow unit testing on individual code bases if necessary. Faster and smaller tests would make adding future tests, functionality, or making changes a lot easier to manage and verify that everything works as intended.
It might be best to also keep a test like the current "data" test as-is for a full run.