Infrastructure/verdaccio
0
Fork 0
mirror of https://github.com/verdaccio/verdaccio.git synced 2024-12-23 22:27:34 -05:00
Code Issues Activity
verdaccio/test
History
Juan Picado @jotadeveloper a5e162d475 feature: Update Build pipeline for Babel transpiler (#349) 
feature: Update Build pipeline for Babel transpiler
2018-01-07 07:59:36 +00:00
..
functional feature: Update Build pipeline for Babel transpiler (#349) 2018-01-07 07:59:36 +00:00
helper feature: Update Build pipeline for Babel transpiler (#349) 2018-01-07 07:59:36 +00:00
integration [GH-131] add cache option to uplinks 2017-06-08 17:59:28 +02:00
unit refactor: These files will be migrated to another repository 2018-01-07 07:59:36 +00:00
.eslintrc feature: Update Build pipeline for Babel transpiler (#349) 2018-01-07 07:59:36 +00:00
mocha.opts feature: Update Build pipeline for Babel transpiler (#349) 2018-01-07 07:59:36 +00: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.