(no subject)
Jul. 7th, 2005 04:28 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
wwilliam47So say that you're going to write a tool for GUI testing that runs test scripts that your users create.
Say that you allow this tool to be run from the command line automatically--"here's a script, please execute it". So far, this is a good and useful thing.
Say that one of your users might, hypothetically speaking, want to do something like put scripts in version control along with the rest of the project, such that a properly licensed developer can check out the project wherever their nefarious filesystem suggests and have everything actually run.
Say that you, being a complete and utter moron, declined to actually allow the tool to run a test script from the command line using a relative path. Because clearly the scenario of multiple developers wanting to collaborate on a project and use automation around your automated test tool would never happen in the Real World(tm).
Not, of course, that I'm bitter about this particular misfeature.
Say that you allow this tool to be run from the command line automatically--"here's a script, please execute it". So far, this is a good and useful thing.
Say that one of your users might, hypothetically speaking, want to do something like put scripts in version control along with the rest of the project, such that a properly licensed developer can check out the project wherever their nefarious filesystem suggests and have everything actually run.
Say that you, being a complete and utter moron, declined to actually allow the tool to run a test script from the command line using a relative path. Because clearly the scenario of multiple developers wanting to collaborate on a project and use automation around your automated test tool would never happen in the Real World(tm).
Not, of course, that I'm bitter about this particular misfeature.
