We have an automated system which checks out automation into some job-centric location (changes with each run of the test) and runs the tests, the results of which are reported under the job number.
This poses a problem for Eggplant tests as far as helpers are concerned. Eggplant has hard-coded paths to helpers.
The ideal solution would be to have helpers use relative paths. This does not seem possible through the standard Eggplant means. I have successfully whacked the helperSuites strings in the SuiteInfo file using relative paths. “Relative path” in Eggplant seems a little capricious. I was able to find a relative path that worked for a simple test case, but I am worried that the idea of relative doesn’t always mean the same thing in Eggplant. That is, the answer to “Relative to what?” seems to change during an Eggplant run.
The other solution we can come up with is to have the automation whack the hard-coded helperSuites strings with the appropriate path for where the automation has decided to put things during a run. Our trouble here is that the automation is checking things out onto a linux file system on a separate machine. There seems to be at least two ways to mount this external file system on the Mac: 1) bsd’s mount command, 2) Finder.
I am afraid this is one of those posts that will be ignored because it seems just too weird or complex to answer. But I would appreciate any pointers or hints.
My questions are:
- Can we tell Eggplant to use relative paths to helpers within Eggplant itself?
1a) What does ‘relative’ mean in Eggplant? Are all helperSuites during a run relative to the same location (like where the original script launched from? or what?)
- How is it best to mount an external linux file system so that I can hackishly change the SuiteInfo helperSuites strings myself. The bsd mount solution sets a path like: /data/mydir/123456, which is great. But using the Finder to map a network drive sets a path like: /Volumes/SOFTWARE;SC-NAS-1/mydir/123456, which is weird.