-
|
I'm attempting to utilize shellspec as the basis for some after-the-fact tests for a couple of functions of mine whose internals require local dynamic updating of PATH in order to optimize file loading; However, each and every one of the tests I've written continues to fail due to PATH being flagged readonly by shellspec before the code runs. As I don't seem to be able to find anything in the docs as to how I might override this behaviour within shellspec, I'm wondering if there's something I'm missing in the docs, or should I abort the use of shellspec for these functions? To my mind, this constitutes a bug - please correct me if I'm wrong. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Are you using the I checked to be sure, but I can't reproduce it. Please provide the version you are using, the execution environment, the output, and the small code that can be reproduced. |
Beta Was this translation helpful? Give feedback.
-
|
TFT @ko1nksm - that's exactly what I wanted. I obviously misunderstood the description/usage of --sandbox - doh !!! |
Beta Was this translation helpful? Give feedback.
Are you using the
--sandboxoption? The PATH will never be readonly unless you use sandbox mode.I checked to be sure, but I can't reproduce it. Please provide the version you are using, the execution environment, the output, and the small code that can be reproduced.