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

[Azure Monitor OpenTelemetry] Use dev-tool to run tests #28805

Merged
merged 6 commits into from
Mar 7, 2024

Conversation

hectorhdzg
Copy link
Member

Packages impacted by this PR

@azure/monitor-opentelemetry
@azure/monitor-opentelemetry-exporter

@hectorhdzg hectorhdzg changed the title [Azure Monitor OpenTelemetry] [Azure Monitor OpenTelemetry] Use dev-tool to run tests Mar 6, 2024
Copy link
Member

@JacksonWeber JacksonWeber left a comment

Choose a reason for hiding this comment

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

LGTM

@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

"test:browser": "npm run unit-test:browser",
"unit-test:browser": "echo skipped",
"unit-test:node": "mocha -r ../../../common/tools/esm-workaround.js -r esm --require source-map-support/register --reporter ../../../common/tools/mocha-multi-reporter.js --reporter-option output=test-results.xml --timeout 1200000 --full-trace \"dist-esm/test/internal/**/*.test.js\"",
"unit-test:node:debug": "mocha --inspect-brk -r ../../../common/tools/esm-workaround.js -r esm --require source-map-support/register --reporter ../../../common/tools/mocha-multi-reporter.js --reporter-option output=test-results.xml --timeout 1200000 --full-trace \"dist-esm/test/internal/**/*.test.js\"",
"unit-test:node": "dev-tool run test:node-ts-input --no-test-proxy=true -- --timeout 1200000 \"test/internal/**/*.test.ts\"",
Copy link
Member

@HarshaNalluru HarshaNalluru Mar 6, 2024

Choose a reason for hiding this comment

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

This is good, but just a little heads up..
we'll be moving to vitest soon for all the packages instead of mocha.

And while the tests are not migrated to vitest yet, we'll have to follow this #28801 in order to consume the core that is upgraded to esm, that would also fix the failures you observed.

PS: I don't have any concern on which commands we use in the short-term as long as the pipelines are green.

@hectorhdzg hectorhdzg merged commit bf4efc7 into Azure:main Mar 7, 2024
23 checks passed
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.

4 participants