0
Fork 0
mirror of https://github.com/verdaccio/verdaccio.git synced 2024-12-16 21:56:25 -05:00
verdaccio/e2e/cli
Juan Picado 18348940c4
e2e: npm search and ping commands (#3386)
* chore: rename folders

* chore: add search tests

* chore: remove old files

* Update pnpm-workspace.yaml

* chore: fix ui

* Update e2e-ci.yml

* chore: renovate deps

* fix build

* chore: add tests
2022-09-19 23:10:38 +02:00
..
cli-commons e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00
e2e-npm6 e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00
e2e-npm7 e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00
e2e-npm8 e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00
e2e-pnpm6 e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00
e2e-pnpm7 e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00
e2e-yarn1 e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00
e2e-yarn2 e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00
e2e-yarn3 e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00
e2e-yarn4 e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00
jest.config.js e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00
README.md e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00

E2E CLI Testing

What is included on these test?

  • Default configuration only
  • Test with all popular package managers (yarn classic and yarn modern (2,3, 4), pnpm 6,7 and npm 6, 7 and 8)

Commands Tested

cmd npm6 npm7 npm8 pnpm6 pnpm7 yarn1 yarn2 yarn3 yarn4
publish
info
audit
install
deprecate
ping
search

notes:

  • yarn search exist in modern but do not use the search registry endpoint

= no tested = tested = no supported

How it works?

Every package manager + version is a package in the monorepo.

The package @verdaccio/test-cli-commons contains helpers used for each package manager.

import { addRegistry, initialSetup, prepareGenericEmptyProject } from '@verdaccio/test-cli-commons';

The registry can be executed with the following commands, the port is automatically assigned.

// setup
const setup = await initialSetup();
registry = setup.registry;
await registry.init();
// teardown
registry.stop();

The full url can be get from registry.getRegistryUrl(). The yarn modern does not allows the --registry so need a more complex step, while others is just enough adding the following to every command.

await yarn({ cwd: tempFolder }, 'install', ...addRegistry(registry.getRegistryUrl()));

The most of the command allow return output in JSON format which helps with the expects.

const resp = await yarn(
  { cwd: tempFolder },
  'audit',
  '--json',
  ...addRegistry(registry.getRegistryUrl())
);
const parsedBody = JSON.parse(resp.stdout as string);
expect(parsedBody.type).toEqual('auditSummary');

Every command should test either console output or in special cases look up the storage manually.

What should not included on these tests?

  • Anything is unrelated with client commands usage, eg: (auth permissions, third party integrations, hooks, plugins)