Infrastructure/verdaccio
0
Fork 0
mirror of https://github.com/verdaccio/verdaccio.git synced 2025-01-27 22:59:51 -05:00
Code Issues Activity

chore: update js to ts extensions

Browse source
This commit is contained in:
Juan Picado @jotadeveloper 2019-07-27 12:55:20 +02:00
parent 9f7bb80d45
commit ea633eb977
No known key found for this signature in database
GPG key ID: 15AA875EF3768142
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
test/README.md
View file

@ -36,7 +36,7 @@ Unit tests aim to test the CLI API and the Web API. The configuration file is lo
#### Testing an endpoint
We have prepared a template at `test/unit/api/api.__test.template.spec.ts` that you can follow to create your own unit test. Only the tests are appended with `.spec.js` which will be found and used by `jest`.
We have prepared a template at `test/unit/api/api.__test.template.spec.ts` that you can follow to create your own unit test. Only the tests are appended with `.spec.ts` which will be found and used by `jest`.
> Feel free to suggest improvements to the template, there is still a lot of room for improvement.
@ -146,7 +146,7 @@ That will help to run small chunk of tests and makes more easy the development.
In order to inspect more information about what is being sended between your test and the mock server, you might take advance of the `debug` library used by `request`, for instance.
```
NODE_DEBUG=request yarn jest test/unit/modules/api/api.spec.ts --coverage=false
NODE_DEBUG=request yarn jest test/unit/modules/api/api.spec.ts --runInBand=true --coverage=false
```
The outcome you will see in your terminal looks like:
@ -203,7 +203,7 @@ The functional tests aim to run only **cli endpoint** and **web point** using re
> Be aware if you change something in the `{root}/src` source code, you must run `yarn code:build` before to be able to see your changes because functional tests use the transpiled code.
All tests must be included in the `test/functional/index.spec.js` file, which bootstraps the whole process. There is only one spec file and **must be only one**.
All tests must be included in the `test/functional/index.spec.ts` file, which bootstraps the whole process. There is only one spec file and **must be only one**.
The jest configuration file is defined in `test/jest.config.functional.js`. The configuration will create a custom environment launching 3 Verdaccio servers with different configurations.
@ -230,7 +230,7 @@ To add a new feature you need to export the feature as a function that take as a
```js
// newFeature.js
// newFeature.ts
export default function(server) {
@ -246,7 +246,7 @@ export default function(server) {
Then import the feature and run the function within the main `describe` block.
```js
// index.spec.js
// index.spec.ts
import newFeature from './newFeature';