-
-
Notifications
You must be signed in to change notification settings - Fork 69
Open
Description
The current test suite takes a while to startup and run - in order, it:
- Deletes the
distdirectory - Builds the source and test files and outputs to the
distdirectory - Copies the test fixtures to the
distdirectory - Runs
ESLint - Runs
Ava
With steps 1-4, it can take 5-10 seconds before any test even runs! When working on a feature, it would be great to be able to run a set of tests in watch mode, so you could have quick feedback on the changes you're making. Currently, that's hard to do, as parts of steps 2 and 3 can't be run in watch mode.
Some potential solutions:
- Update
cpy-clito add a watch mode- see Add
--watchoption sindresorhus/cpy-cli#16, which says the feature must first be added in sindresorhus/cpy cpyhas a blocker on Add tests for fixed recursive bugs [NO NEW FEATURES WILL BE ADDED UNTIL THIS IS DONE] sindresorhus/cpy#99
- see Add
- Use a bundler for building/testing
- Something like Rollup would make building/copying/watching (and in the right order) fairly straightforward
- Restructure the
fixturesdirectory to allow symlinking to thedistdirectory - Use something like
ts-nodeto test TypeScript files directly, without a build step
I'd be open to making a PR for any of these, but I'm not familiar with the issue in cpy to add test cases for it. Personally, I'm fairly familiar with Rollup.
kaisermann, steckhelena and andreww2012
Metadata
Metadata
Assignees
Labels
No labels