Add a simple test suite for cd commands #51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a test suite for the
cd
command that I used to verify the correctness of #37. I pulled injest
as the test runner, but the same idea could be implemented easily with another option.To run the tests,
npm test
.As written, the codebase relies on a shared global namespace which happens naturally in the browser, but not-so-naturally when running tests from the command line, so I had to put in a hacky
global.whatever =
prelude to get things set up before the tests run. In order to getrequire
to work, I addedmodule.exports
to the ends of the necessary files, and guarded those with a check so that when the same code runs in browser (with nomodule
global) it won't complain.Lemme know if you prefer a different set of hacks! I imagine without bringing in a build system, something like what's here is going to be one of the better options.