Track Maintenance: will journey-script-tests continue to work?

_Imported from https://github.com/exercism/-DEPRECATED-PLEASE-USE-exercism.io-REPO-v2-feedback/issues/64._
_Originally posted by @NobbZ._

#

From my userpoint of view, the process of retrieving has changed massively, I now do even need approval by a mentor.

But from a track-maintainers way, who uses a journey-script for testing the track, it worries me.

Those journey-scripts set up a mini-exercism on travis, which does only know about a single track. Also the CLI is used to fetch exercises from the mini-exercism.

This way of testing does not only ensure, that the tests and example solution do work, but also that all files are served correctly (not getting mangled because of symlink, or accidentaly match ignore pattern, etc).

Will such a script still be possible with nextercism CLI and API? I do not mind to change it a bit to make it suite the new CLI commands or because the mini-exercism has to be set up differently, I mean in general… Or do I need to go back to a script which simply walks the file tree and runs the test without pulling them?