alvis
/
nvm
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
1393 Commits
1 Branch
90 Tags
3.7 MiB
Tree: 24a9c089ff
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '24a9c089ff'
${ noResults }
Commit Graph

2 Commits (24a9c089ffb83f29be30ae55e3c2667c66c7bb20)

Author SHA1 Message Date
Jordan Harband 73aa35f508
[Tests] use `$NVM_DIR` instead of relative paths
9 years ago
Jordan Harband c9b7ccdaea
Run `node` and `io.js` installation test suites separately.
9 years ago
Jordan Harband 9615672243 Move node-specific installation tests to their own directory.
10 years ago
Jordan Harband 1931f7f3f8 Remove '-e' option from installation tests, in favor of explicit failures.
11 years ago
Jordan Harband 354be52672 Correct installation test paths
11 years ago
Jordan Harband ba08fa31d8 Moving actual installation tests to their own suite.
11 years ago
Jordan Harband bb01513eba Making sure there's test coverage for `nvm i`
11 years ago
Jordan Harband 4cf940153c Use node 0.9 for these testsso that people aren't likely to have it installed
11 years ago
Jordan Harband eb6031cb58 Clean up after existing `nvm install` tests.
11 years ago
Jordan Harband 55a6f1f06e Organizing `nvm install` tests better.
11 years ago
Jordan Harband b15ea07067 Don't clobber the latest version of 0.10 for tests.
11 years ago
messju mohr e46ee7b30b added test for using the latest of two versions
11 years ago