It seems that doo constructs an absolute file URI for phantom to open in order to run the tests. The problem I've run into is that the following is a valid file path on linux: /home/user/code/feature%2Fbranch but when such things are passed to the browser as a file URI it interprets the encoding (presumably) as /home/user/code/feature/branch which doesn't exist.
This is common when running on jenkins which uses these kinds of paths to set up the workspace for git branches of the form feature/thing or hotfix/bug.
It seems that doo constructs an absolute file URI for phantom to open in order to run the tests. The problem I've run into is that the following is a valid file path on linux:
/home/user/code/feature%2Fbranchbut when such things are passed to the browser as a file URI it interprets the encoding (presumably) as/home/user/code/feature/branchwhich doesn't exist.This is common when running on jenkins which uses these kinds of paths to set up the workspace for git branches of the form
feature/thingorhotfix/bug.