2021-07-11 15:42:56 +02:00
---
id: e2e
title: "End to End testing"
---
2022-02-05 19:39:12 +01:00
### Testing the integrity of React components by publishing in a private registry
2021-09-13 22:14:09 +02:00
2022-02-05 19:39:12 +01:00
> The final stage of a react component is when it is being published and distributed. How can I ensure my packages won’ t crash in production? This talk will help you to test your React components by publishing them to a private registry and running End-to-End tests against them.
< iframe width = "300" height = "600" src = "https://www.youtube.com/embed/bRKZbrlQqLY" title = "YouTube video player" frameborder = "0" allow = "accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen > < / iframe >
2021-09-13 22:14:09 +02:00
- [Slides ](https://docs.google.com/presentation/d/1a2xkqj1KlUayR1Bva1bVYvavwOPVuLplxFtup9MI_U4/edit?usp=sharing )
- [Demo ](https://github.com/juanpicado/verdaccio-end-to-end-tests )
2022-02-05 19:39:12 +01:00
## End to End and Verdaccio
2021-09-13 22:14:09 +02:00
2022-02-05 19:39:12 +01:00
Some projects organize packages in multi-packages repositories or [monorepos ](https://github.com/babel/babel/blob/master/doc/design/monorepo.md ). End to End testing is a topic that usually is only relevant for User Interfaces, but from a Node.js perspective, **publishing packages also need to be tested** .
2021-07-11 15:42:56 +02:00
Such approach has been really hard to achieve considering:
* Populate canary packages on public services seems not to be a good idea
* Some self-hosted OSS registries are too heavy
* Offline environments (private networks)
**Verdaccio** is a lightweight registry with zero-configuration that **fits perfectly in any E2E + CI workflow** .
2021-07-27 21:52:49 +02:00
## Implementation {#implementation}
2021-07-11 15:42:56 +02:00
There is no a silver bullet yet, each implementation seems to be specific for each project, you can check some of them in
the following thread [clicking here ](https://stackoverflow.com/a/50222427/308341 ).
2022-02-05 19:39:12 +01:00
## Examples in Open Source
The following projects have examples using Verdaccio in Open Source
### Bash Examples
* [Babel.js ](https://github.com/babel/babel ) *(+35k ⭐️)*
2022-03-05 09:14:43 +01:00
* [Docusaurus ](https://github.com/facebook/docusaurus ) *(+31k ⭐️)*
2022-02-05 19:39:12 +01:00
* [create-react-app ](https://github.com/facebook/create-react-app/blob/master/CONTRIBUTING.md#contributing-to-e2e-end-to-end-tests ) *(+73.5k ⭐️)*
* [Uppy ](https://github.com/transloadit/uppy ) *(+21k ⭐️)*
* [ethereum/web3.js ](https://github.com/ethereum/web3.js ) *(+8k ⭐️)*
2022-03-05 09:14:43 +01:00
* [adobe react-spectrum ](https://github.com/adobe/react-spectrum/pull/2432 ) *(+6k ⭐️)*
2022-02-05 19:39:12 +01:00
* [Mozilla Neutrino ](https://github.com/neutrinojs/neutrino ) *(+3k ⭐️)*
2021-07-11 15:42:56 +02:00
This is the most simple example using Verdaccio in a bash script (extracted from *create-react-app* ).
```bash
#!/bin/sh
set -e
local_registry="http://0.0.0.0:4873"
# start local registry
tmp_registry_log=`mktemp`
sh -c "mkdir -p $HOME/.config/verdaccio"
sh -c "cp --verbose /config.yaml $HOME/.config/verdaccio/config.yaml"
sh -c "nohup verdaccio --config $HOME/.config/verdaccio/config.yaml & >$tmp_registry_log & "
# wait for `verdaccio` to boot
grep -q 'http address' < (tail -f $tmp_registry_log)
# login so we can publish packages
sh -c "npm-auth-to-token -u test -p test -e test@test.com -r $local_registry"
# Run nmp command
sh -c "npm --registry $local_registry publish"
```
2022-02-05 19:39:12 +01:00
### Docker Examples
2021-07-11 15:42:56 +02:00
2022-02-05 19:39:12 +01:00
* [Hyperledger ](https://github.com/hyperledger/fabric-chaincode-node )
### Programtically Examples
2021-07-11 15:42:56 +02:00
* [Storybook ](https://github.com/storybooks/storybook ) *(+44k ⭐️)*
* [Gatsby ](https://github.com/gatsbyjs/gatsby ) *(+40k ⭐️)
2022-02-05 19:39:12 +01:00
#### Verdaccio module
Via CLI:
2021-07-11 15:42:56 +02:00
* [Aurelia Framework ](https://github.com/aurelia ) *(+12k ⭐️)*
2022-03-05 09:14:43 +01:00
* [Netlify CLI ](https://github.com/netlify/cli ) *(+1k ⭐️)*
2022-02-05 19:39:12 +01:00
* [Embark ](https://embark.status.im/ ) *(+3k ⭐️)*
2022-03-05 09:14:43 +01:00
* [Microsoft Beachball ](https://github.com/microsoft/beachball )
2022-02-05 19:39:12 +01:00
#### Node.js `child_process` examples
* [Angular CLI ](https://github.com/angular/angular-cli ) *(+25k ⭐️)*
2021-07-11 15:42:56 +02:00
* [bit ](https://github.com/teambit/bit ) *(+6k ⭐️)*
* [pnpm ](https://github.com/pnpm/pnpm ) *(+6k ⭐️)*
2022-03-05 09:14:43 +01:00
* [aws-sdk cli v3 ](https://github.com/aws/aws-sdk-js-v3 ) *(+1k ⭐️)*
* [angular-eslint ](https://github.com/angular-eslint/angular-eslint ) *(+1k ⭐️)*
2022-02-05 19:39:12 +01:00
2022-06-22 23:12:10 +02:00
## Example repositories
2021-07-11 15:42:56 +02:00
2022-06-22 23:12:10 +02:00
- [e2e-ci-example-gh-actions ](https://github.com/juanpicado/e2e-ci-example-gh-actions )
- [verdaccio-end-to-end-tests ](https://github.com/juanpicado/verdaccio-end-to-end-tests )
- [verdaccio-fork ](https://github.com/juanpicado/verdaccio-fork )
2021-07-11 15:42:56 +02:00