separate script_path encourages tests to miss common scenarios

Issue #4 resolved
Dave Abrahams
created an issue

scripttest always invokes executables with fully-qualified paths, and can end up selecting an executable invoked without qualification that can't be found via PATH. Aside from being surprising (and undocumented?), it is impossible to test the normal usage. Yes, it's important to hit the corner cases, but it's important to make sure testing covers the common cases well. I think you should leave the qualification/no-qualification thing up to the user, who can figure it out.

Comments (3)

  1. Ian Bicking repo owner

    Hmm... maybe there's no real purpose to making the executable fully qualified. I think it might have simply been an unnecessary desire to be explicit.

  2. Log in to comment