Skip to content
This repository has been archived by the owner on Sep 6, 2023. It is now read-only.

Add after-publish / after-package integration tests #59

Open
Bnaya opened this issue Oct 13, 2020 · 1 comment
Open

Add after-publish / after-package integration tests #59

Bnaya opened this issue Oct 13, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@Bnaya
Copy link
Contributor

Bnaya commented Oct 13, 2020

Our current integration tests are running agains the source in the repo/build code,
via workspace and not real npm package (or tarballs)

In the real world, the code will run from inside npm package
It's very possible that something will get wrong in the packaging/publishing process (eg different paths)

We need to create an infra that will let us to run the same integration tests that we have against the to-be-published packages (using tarball or verdaccio local registry)

It's very important to also test the CLI inside each package

@Bnaya Bnaya added the enhancement New feature or request label Oct 13, 2020
@gioragutt
Copy link
Contributor

How about create an inner project with root-cause specified in package.json as "root-cause-core": "../../path/to/root/cause/in/the/repo"?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants