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

Build: Fix test in core-common being ignored #27068

Merged
merged 1 commit into from May 15, 2024

Conversation

43081j
Copy link
Contributor

@43081j 43081j commented May 8, 2024

One of the get-renderer-name tests is failing, but this goes uncaught since vitest does not understand node's test runner output.

This basically moves to using it from vitest rather than node:test, thus introducing a failing test. The failing test has then been fixed.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

  • stories
  • unit tests
  • integration tests
  • end-to-end tests

Manual testing

N/A (unit test update)

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts

  • Make sure this PR contains one of the labels below:

    Available labels
    • bug: Internal changes that fixes incorrect behavior.
    • maintenance: User-facing maintenance tasks.
    • dependencies: Upgrading (sometimes downgrading) dependencies.
    • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
    • cleanup: Minor cleanup style change. Will not show up in release changelog.
    • documentation: Documentation only changes. Will not show up in release changelog.
    • feature request: Introducing a new feature.
    • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
    • other: Changes that don't fit in the above categories.

One of the `get-renderer-name` tests is failing, but this goes uncaught
since vitest does not understand node's test runner output.

This basically moves to using `it` from vitest rather than `node:test`,
thus introducing a failing test. The failing test has then been fixed.
Copy link

nx-cloud bot commented May 8, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 0245d8b. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 1 target

Sent with 💌 from NxCloud.

@JReinhold JReinhold added build Internal-facing build tooling & test updates ci:normal test labels May 13, 2024
@JReinhold JReinhold self-assigned this May 13, 2024
Copy link
Contributor

@JReinhold JReinhold left a comment

Choose a reason for hiding this comment

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

thanks for this

@JReinhold JReinhold changed the title test(core-common): migrate to vitest test functions Build: Fix test in core-common being ignored May 15, 2024
@JReinhold JReinhold merged commit 41c15fc into storybookjs:next May 15, 2024
56 of 58 checks passed
@github-actions github-actions bot mentioned this pull request May 15, 2024
13 tasks
@43081j 43081j deleted the cc-test branch May 15, 2024 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Internal-facing build tooling & test updates ci:normal test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants