-
Notifications
You must be signed in to change notification settings - Fork 14
Document test process and/or fix tests #2
Comments
I might get this engraved on a plaque and nail it to my desk. Story of my life. |
I meant to put an issue in for this, sorry. The problem is that to test an npm import, it needs a module to import less from - now I used less v2 - but I have specified with .npmignore not to include test files, so it was a short term thing. My current ideas for a long term way of testing are Any preferences? You'll have the same problem with bower. And I explained on the pull request why I don't want an optional dependency just yet.. Sorry things are in limbo, I only wrote this yesterday, I wasn't expecting someone to want it documented before the next day... |
went for (a) so I can test multiple scenarios without searching for arbitrary packages. Fixed. |
? Really?! |
I was expecting a thanks for resolving both issues for you. |
I apologize for escalating. Assuming you're OK with it, I'd like to put this behind us and concentrate on solving the task at hand. Should |
Tbh I don't know much about bower, but yes I could change it to be a |
OK, cool. I'll test against that module for now and we can leave renaming/adding files for later. |
Should the tests pass? If so, can you update the README to include testing instructions?
I planned on using this as the starting point for less-plugin-bower-import but stopped when I couldn't get the tests to pass. Here's what I did:
My first attempt, after cloning the repo:
I installed less (and added it as a dependency) then tried again:
I looked at the test and saw it was using Less's tests, so I went to that directory, installed Less's dependencies and tried again:
Better, but still broken. I'm not sure if it's me, the code, or some combination of the two.
The text was updated successfully, but these errors were encountered: