Infrastructure/verdaccio
0
Fork 0
mirror of https://github.com/verdaccio/verdaccio.git synced 2024-12-16 21:56:25 -05:00
Code Issues Activity
verdaccio/test
History
Ryan Graham 64c3ea445b
don't blindly clobber local dist-tags 
If packages are being published to verdaccio as well as upstream to
npmjs.org, then when the cache is updated from npmjs.org it uses the
dist-tags from the upstream even if the locally published version is
actually newer. This makes it very difficult to use verdaccio as a
staging registry for testing out potential releases.

This change partially reverts a change in behaviour that was introduced
in #8 which caused a regression for the staging style workflow that was
supported by sinopia.
2017-06-01 13:59:56 -07:00
..
functional Apply partially new eslint rules, upgrade es6 and replace octal literals by chalk colors 2017-04-23 22:19:31 +02:00
integration renaming 'sinopia' to verdaccio. 2016-11-07 12:15:38 -05:00
unit don't blindly clobber local dist-tags 2017-06-01 13:59:56 -07:00
.eslintrc Apply partially new eslint rules, upgrade es6 and replace octal literals by chalk colors 2017-04-23 22:19:31 +02:00
mocha.opts update mocha to 2.2.3+, + options file 2015-04-07 22:51:05 +03:00
README.md renaming 'sinopia' to verdaccio. 2016-11-07 12:15:38 -05:00

README.md

All tests are split in three folders:

  • unit - Tests that cover functions that transform data in an non-trivial way. These tests simply require() a few files and run code in there, so they are very fast.
  • functional - Tests that launch a verdaccio instance and perform a series of requests to it over http. They are slower than unit tests.
  • integration - Tests that launch a verdaccio instance and do requests to it using npm. They are really slow and can hit a real npm registry.

Unit and functional tests are executed automatically by running npm test from the project's root directory. Integration tests are supposed to be executed manually from time to time.