verdaccio/test
Meeeeow 38518baf44 fix: search leak private package and ui bug
- Check permission in search API
- Fix author's name not show in search result
2017-04-21 11:53:05 +08:00
..
functional Remove Symbols dependency, Node 4 as min version supported 2017-04-17 11:36:35 +02:00
integration renaming 'sinopia' to verdaccio. 2016-11-07 12:15:38 -05:00
unit fix: search leak private package and ui bug 2017-04-21 11:53:05 +08:00
.eslintrc set up some linting (obvious errors only) 2015-03-28 21:25:53 +03:00
README.md renaming 'sinopia' to verdaccio. 2016-11-07 12:15:38 -05:00
mocha.opts update mocha to 2.2.3+, + options file 2015-04-07 22:51:05 +03: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.