--- id: e2e title: "End to End testing" --- ### Testing the integrity of React components by publishing in a private registry > 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. - [Slides](https://docs.google.com/presentation/d/1a2xkqj1KlUayR1Bva1bVYvavwOPVuLplxFtup9MI_U4/edit?usp=sharing) - [Demo](https://github.com/juanpicado/verdaccio-end-to-end-tests) ## End to End and Verdaccio 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**. 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**. ## Implementation {#implementation} 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). ## Examples in Open Source The following projects have examples using Verdaccio in Open Source ### Bash Examples * [Babel.js](https://github.com/babel/babel) *(+35k ⭐️)* * [Docusaurus](https://github.com/facebook/docusaurus) *(+31k ⭐️)* * [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 ⭐️)* * [adobe react-spectrum](https://github.com/adobe/react-spectrum/pull/2432) *(+6k ⭐️)* * [Mozilla Neutrino](https://github.com/neutrinojs/neutrino) *(+3k ⭐️)* 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" ``` ### Docker Examples * [Hyperledger](https://github.com/hyperledger/fabric-chaincode-node) ### Programtically Examples * [Storybook](https://github.com/storybooks/storybook) *(+44k ⭐️)* * [Gatsby](https://github.com/gatsbyjs/gatsby) *(+40k ⭐️) #### Verdaccio module Via CLI: * [Aurelia Framework](https://github.com/aurelia) *(+12k ⭐️)* * [Netlify CLI](https://github.com/netlify/cli) *(+1k ⭐️)* * [Embark](https://embark.status.im/) *(+3k ⭐️)* * [Microsoft Beachball](https://github.com/microsoft/beachball) #### Node.js `child_process` examples * [Angular CLI](https://github.com/angular/angular-cli) *(+25k ⭐️)* * [bit](https://github.com/teambit/bit) *(+6k ⭐️)* * [pnpm](https://github.com/pnpm/pnpm) *(+6k ⭐️)* * [aws-sdk cli v3](https://github.com/aws/aws-sdk-js-v3) *(+1k ⭐️)* * [angular-eslint](https://github.com/angular-eslint/angular-eslint) *(+1k ⭐️)* ## Example repositories - [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)