Skip to content

test(performance-tests): create performance test package#7864

Draft
siddsriv wants to merge 4 commits intomainfrom
perf-tests
Draft

test(performance-tests): create performance test package#7864
siddsriv wants to merge 4 commits intomainfrom
perf-tests

Conversation

@siddsriv
Copy link
Copy Markdown
Contributor

@siddsriv siddsriv commented Mar 18, 2026

Issue

Internal JS-6417

Description

Prepare a new performance tests package (JSv3 SDK: operational)

  • First metric: we start with refactoring the existing bundle size measurement infra in the SDK, to be used in the new performance-tests package for json outputs to stdout, instead of markdown reports.

Testing

test.sh serves as the entry point for running performance tests, and will output results to stdout.

Checklist

  • If the PR is a feature, add integration tests (*.integ.spec.ts) or E2E tests.
    • It's not a feature.
  • My E2E tests are resilient to concurrent i/o.
    • I didn't write any E2E tests.
  • I added access level annotations e.g. @public, @internal tags and enabled doc generation on the package. Remember that access level annotations go below the description, not above.
    • I didn't add any public functions.
  • Streams - how do they work?? My WebStream readers/locks are properly lifecycled. Node.js stream backpressure is handled. Error handling.
    • No streams here.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@@ -0,0 +1,6 @@
#!/usr/bin/env bash
set -euo pipefail
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

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.

1 participant