npmpackage.info

Gathering detailed insights and metrics for @fluidframework/azure-scenario-runner

@fluidframework/azure-scenario-runner - 1.2.0 | npmpackage.info

@fluidframework/azure-scenario-runner

Library for building distributed, real-time collaborative web applications

1.2.0

4,839

MIT

TypeScript

389.42 kB

6.3

Installations

npm install @fluidframework/azure-scenario-runner

Developer Guide

BETA

Typescript

No

Module System

N/A

Node Version

18.17.1

NPM Version

6.14.18 Pull Requests

Open

75

Total

21,591

Closed

3,005

Merged

18,511

Issues

Open

22

Total

3,291

Closed

3,269

Releases

244

Fluid Framework v2.50.0 (minor)

client_v2.50.0

Updated on Jul 07, 2025

Fluid Framework v2.43.0 (minor)

client_v2.43.0

Updated on Jun 24, 2025

Fluid Framework v2.42.0 (minor)

client_v2.42.0

Updated on Jun 10, 2025

Fluid Framework v2.41.0 (minor)

client_v2.41.0

Updated on May 27, 2025

Fluid Framework v2.40.0 (minor)

client_v2.40.0

Updated on May 12, 2025

Fluid Framework v2.33.2 (patch)

client_v2.33.2

Updated on May 01, 2025

View All 244 releases

Languages

TypeScript

JavaScript

HTML

Dockerfile

Shell

Mustache

Batchfile

TypeScript (89.39%)

JavaScript (9.39%)

HTML (1.12%)

Dockerfile (0.06%)

Shell (0.03%)

Mustache (0.01%)

Developer

microsoft

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

4,839 Stars

22,747 Commits

553 Forks

76 Watchers

528 Branches

251 Contributors

Updated on Jul 14, 2025

Maintainers

View All 251 Contributors

Package Meta Information

Latest Version

1.2.0

Package Id

@fluidframework/azure-scenario-runner@1.2.0

Unpacked Size

389.42 kB

Size

55.14 kB

File Count

137

NPM Version

6.14.18

Node Version

18.17.1

Published on

Apr 11, 2024

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

Dev Dependencies

@fluid-tools/build-cli @fluidframework/build-common @fluidframework/eslint-config-fluid @types/js-yaml @types/mocha @types/nock @types/node @types/uuid concurrently eslint nock nyc prettier rimraf typescript

@fluidframework/azure-scenario-runner

Azure Scenario Runner

This package provides a reference application that executes pre-set scenarios with the intent of measuring the Fluid Framework's performance and reliability. We primarily use this package as part of a pipeline scheduled to run periodically to measure, log, and report various performance and reliability metrics. These metrics can then be used to gauge an undrestanding of the expected behavior/performance of the Fluid Framework in these various scenarios, which can help define the SLA.

Implemented Scenarios

Azure Client

Tests creating an Azure Client

Doc Creator

This scenario creates a bunch of empty Fluid documents and measures the time it takes to create theses documents.

Doc Loader

This scenario loads a set of previously created docs multiple times and measures the time it takes to load these documents.

Map Traffic

[TBD]

Guides

Running the perf tests locally

Set the azure__fluid__relay__service__tenantId environment variable to equal your FRS TenantID
Set the azure__fluid__relay__service__tenantKey environment variable to equal your FRS Tenant's Primary Key
Set the azure__fluid__relay__service__function__url environment variable to equal your FRS Service Function URL
Set the azure__fluid__relay__service__endpoint environment variable to equal the Alfred endpoint of your FRS tenant
(Optional) Set the azure__fluid__relay__service__region environment variable to equal the region of your FRS tenant (eg. westus2, westus3, eastus, westeurope)
Run the test with npm run start

Configuring the test configuration

The test configuration file testConfig_v1.yml can be configured to modify the parameters of each scenario and the order they're run in.

Adding New Scenarios

[TBD]

Scenario runnner for FRS and Azure Local Service. This package can be used to create and execute various scenarios involving azure-client, IFluidContainer and a range of distributed data structures (DDSes), while collecting telemetry and validating state in the process. Scenarios are sourced via yaml config files.

Appendix

Contribution Guidelines

There are many ways to contribute to Fluid.

Participate in Q&A in our GitHub Discussions.
Submit bugs and help us verify fixes as they are checked in.
Review the source code changes.
Contribute bug fixes.

Detailed instructions for working in the repo can be found in the Wiki.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

This project may contain Microsoft trademarks or logos for Microsoft projects, products, or services. Use of these trademarks or logos must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.

Help

Not finding what you're looking for in this README? Check out our GitHub Wiki or fluidframework.com.

Still not finding what you're looking for? Please file an issue. Thank you!

Trademark

This project may contain Microsoft trademarks or logos for Microsoft projects, products, or services. Use of these trademarks or logos must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

10

License

Determines if the project has defined a license.

10

Security-Policy

Determines if the project has published a security policy.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

8

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

5

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Signed-Releases

Determines if the project cryptographically signs release artifacts.

0

SAST

Determines if the project uses static code analysis.

0

Fuzzing

Determines if the project uses fuzzing.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

6.3

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More