How to run the tests locally?

[PeterDaveHello]

I tried the instructions as readme says, but there are always errors there like:

+ rm -Rf v* src alias
+ mkdir src alias
    Aliases
    ✓ "nvm alias" should not accept aliases with slashes
    ✓ "nvm unalias" should not accept aliases with slashes
    ✓ Running "nvm alias <aliasname> <target>" again should change the target
    ✓ Running "nvm alias <aliasname>" should list but one alias.
    ✓ Running "nvm alias" lists implicit aliases when they do not exist
    ✓ Running "nvm alias" lists manual aliases instead of implicit aliases when present
    ✓ Running "nvm alias" should list all aliases.
      circular
      ✓ nvm_resolve_alias
      ✓ nvm_resolve_local_alias

      lts
N/A: version "N/A -> N/A" is not yet installed.

You need to run "nvm install N/A" to install it before using it.
mv: cannot move '/usr/bin/alias/lts' to '/usr/bin/alias/lts.bak': Permission denied
rm: cannot remove '/usr/bin/alias/lts/*': Permission denied
rm: cannot remove '/usr/bin/alias/lts/boron': Permission denied
rm: cannot remove '/usr/bin/alias/lts/argon': Permission denied
      ✗ "nvm alias" should ensure LTS alias dir exists

Tried on Ubuntu 12.04, 14.04 and 16.04, none of them can directly pass the test. Is there anything special need to be setup? I also tried to run travis ci with Ubuntu 14.04 (See https://travis-ci.org/PeterDaveHelloKitchen/nvm/builds/178530168), the tests also failed.

Thanks.

[ljharb]

The tests currently only work in the default location of NVM_DIR, i.e. $HOME/.nvm.

Regardless, the nvm dir should not be located in /usr/bin since it's a per-user tool.

[PeterDaveHello]

yes it's not in /usr/bin, it's under my home directory, I'll try with $HOME/.nvm

[ljharb]

Related: #708, #719, #949, #357, #589.

[PeterDaveHello]

oops ... so many related issues 😰

[PeterDaveHello]

still failed lol ...

@ljharb would you like to write a Dockerfile, packer or vargrat template to help build a local development environment can pass the test peoperly? I thought this can help decrease the gap to involve in nvm development :) Many thanks.

[ljharb]

I'd be happy to review adding one, but I don't use any of those tools myself.

[PeterDaveHello]

If you can tell me how to setup the environment properly I think I can write at least one of them 😄

[PeterDaveHello]

I think the problem here is nobody knows how to make it works in a clean environment, even on Travis CI, it can only pass the tests on Ubuntu Precise but can't on Ubuntu Trusty, which makes no sense to me, doesn't it seem to be OS independent? I think we could try to make sure the process on Ubuntu 14.04 about how to build an environment can run the tests.

[ljharb]

The issue with trusty vs precise is that the generic image on trusty doesn't preinstall many things that nvm depends on - the tests should pass without changes on trusty provided that the right dependencies are installed, theoretically.

[PeterDaveHello]

@ljharb I think I installed the missing packages, the error messages are not come from the missing command or package, would you like to take a look? Since if it's just about missing packages, could be very easy to solved, right?

[PeterDaveHello]

https://travis-ci.org/PeterDaveHelloKitchen/nvm/jobs/179399513

[ljharb]

npm isn't a "missing package" - but yeah I'm not really sure why those fail.

[PeterDaveHello]

just testing, the test will fail in a strange place without npm package ...

[PeterDaveHello]

Got one point here, the account needs to have sudo permission without password, found some sudos in the tests.

@ljharb would you be happy to help sort this out so that we can make sure contributors can develop faster and more reliable? The current test process that can only run on Travis CI is not that friendly, thanks.