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 0a6668c060
chore: update versions (6-next) (#3593)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2023-02-05 21:58:06 +01:00
..
cli-commons chore: update versions (6-next) (#3593) 2023-02-05 21:58:06 +01:00
e2e-npm6 fix(deps): update all core dependencies (#3542) 2022-12-26 09:43:07 +01:00
e2e-npm7 chore: list stars of an user (#3451) 2022-10-21 23:05:18 +02:00
e2e-npm8 fix(deps): update all core dependencies (#3507) 2022-11-21 18:40:22 +01:00
e2e-npm9 fix(deps): update all core dependencies (#3542) 2022-12-26 09:43:07 +01:00
e2e-pnpm6 chore: list stars of an user (#3451) 2022-10-21 23:05:18 +02:00
e2e-pnpm7 chore: list stars of an user (#3451) 2022-10-21 23:05:18 +02:00
e2e-yarn1 e2e: command dist-tag (#3390) 2022-09-24 08:53:03 +02:00
e2e-yarn2 chore(deps): bump actions/upload-artifact from 3.1.1 to 3.1.2 (#3561) 2023-01-13 20:38:39 +01:00
e2e-yarn3 chore(deps): bump actions/upload-artifact from 3.1.1 to 3.1.2 (#3561) 2023-01-13 20:38:39 +01:00
e2e-yarn4 e2e: yarn publish (#3393) 2022-09-27 22:56:17 +02:00
jest.config.js e2e: npm search and ping commands (#3386) 2022-09-19 23:10:38 +02:00
README.md chore: list stars of an user (#3451) 2022-10-21 23:05:18 +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 RC)
  • pnpm 6, 7
  • npm 6, 7, 8 and 9

Commands Tested

cmd npm6 npm7 npm8 npm9 pnpm6 pnpm7 yarn1 yarn2 yarn3 yarn4
publish
info
audit
install
deprecate
ping
search
star
stars
dist-tag

notes:

  • yarn search cmd exist in modern but, it do not uses the search registry endpoint.
  • yarn modern has two info commands, the one used here is yarn npm info

= 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)