Skip to main content

Pruebas End to End

Testing the integrity of React components by publishing in a private registry

E2E and Verdaccio

Algunos projectos organizan paquetes en multi repositorios o mono repositorios. Pruebas E2E es un tema que usualmente es solo relevante para Interfaces de Usuario, pero desde el punto de vista de Node.js, los paquetes que publicamos tambien debe ser probados.

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.


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.

Example using Bash

This is the most simple example using Verdaccio in a bash script (extracted from create-react-app).


set -e


# start local registry
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 -r $local_registry"
# Run nmp command
sh -c "npm --registry $local_registry publish"

Who is using it for E2E?