contrib: break out tests into separate files for each plugin #36
Comments
Maybe you should have to files: bundle.js and bundle-test.js. |
I actually don't think the tests need to be bundled. I need to figure out how to get npm test to figure out which tests are appropriate to run or not. |
So one test file for each plugin, then a single test file that will run the tests that are given by some prereq? What would that be? The ones bundled? User selected? Don't know? |
Shrugs. I think maybe all plugins present... but then, someone may build a subset (supported by bundle) and want to test only those. Not sure. what to do here. That's why it's an open issue for so long. |
I was thinking about a --test option to bundle.js. The default would be all, but otherwise you could specify which tests you want. |
That could work. If you specify, it tests your bundle (maybe before writing to the file?) but if not, the npm test command tests all in the one big bundle. |
In addition, bundle.js needs to optionally include a test only if building with the plugin in question.
The text was updated successfully, but these errors were encountered: