Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(cli): support excluding projects with --project=!pattern #6924

Merged
merged 3 commits into from
Nov 19, 2024

Conversation

haines
Copy link
Contributor

@haines haines commented Nov 18, 2024

Description

This PR allows a leading ! to negate patterns in the --project option, making it possible to exclude certain projects when running vitest.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
  • Ideally, include a test that fails without this PR but passes with it.
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

  • Run the tests with pnpm test:ci.

Documentation

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

Copy link

netlify bot commented Nov 18, 2024

Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit f0c9035
🔍 Latest deploy log https://app.netlify.com/sites/vitest-dev/deploys/673b2b8ef3cd900008ef371e
😎 Deploy Preview https://deploy-preview-6924--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -7,6 +7,9 @@ test.each([
{ pattern: '*j*', expected: ['project_1', 'project_2'] },
{ pattern: 'project*', expected: ['project_1', 'project_2'] },
{ pattern: 'space*', expected: ['space_1'] },
{ pattern: '!project_1', expected: ['project_2', 'space_1'] },
{ pattern: '!project*', expected: ['space_1'] },
{ pattern: '!project', expected: ['project_1', 'project_2', 'space_1'] },
])('should match projects correctly: $pattern', async ({ pattern, expected }) => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, this test seems a bit flawed. What about adding something like this?

expect(ctx.projects.map(p => p.name)).toEqual(expected)

Note: await runVitest returns ctx

@haines haines requested a review from sheremet-va November 18, 2024 15:37
root: 'fixtures/project',
reporters: ['basic'],
project: pattern,
})

expect(stderr).toBeFalsy()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to remove other assertions - they assert the reporter behaviour (what users see). stderr is especially important - we should be able to see what's wrong without reruning the test

@haines haines requested a review from sheremet-va November 18, 2024 17:38
@sheremet-va sheremet-va merged commit ebfe942 into vitest-dev:main Nov 19, 2024
17 checks passed
@sheremet-va
Copy link
Member

LGTM!

@haines
Copy link
Contributor Author

haines commented Nov 19, 2024

Awesome, thanks!

@haines haines deleted the exclude-projects branch November 19, 2024 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants