Skip to content

Simulator Deployment and Configuration #35

@DakotaCondos

Description

@DakotaCondos

As a DevOps team member,
I want the simulator to be deployable as a continuously running .NET service in Azure,
so that it can integrate with Azure resources and support repeatable project demonstrations.

Acceptance Criteria

  • Given the simulator is deployed
    When the application starts
    Then it initializes the configured bot network and begins simulation.

  • Given the simulator is running
    When bot objects generate events
    Then the simulator routes those events to the configured Azure Event Hub.

  • Given environment-specific configuration is needed
    When the simulator is deployed
    Then settings such as bot count, Event Hub connection information, and secrets are managed outside source code.

  • Given code changes are made
    When the CI/CD pipeline runs
    Then the simulator can be built, tested, and deployed through the team’s deployment process.

  • Given tests are executed
    When the test suite runs
    Then key behaviors such as order routing, stock validation, stock reservation, queue handling, telemetry generation, and delivery completion are verified.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions