NBomber v3.3.0

NBomber

• Client factory refactoring
• Added support of custom step order into NBomber Community version
• Added support of step interception into NBomber Community version
• Added support of ReportingSink into NBomber Community version
• Added functionality to load configs by URL
• DefaultMaxFailCount = 5_000

NBomber v3.2.2

NBomber

• Fixed issue with displaying reporting on console for cluster
• Refactored stats rounding (removed extra memory allocations)
• Fixed issue with running live table for ApplicationType.Process
• Cosmetic changes for reporting

NBomber.Cluster

• Added in-place stats rounding
• Refactored passing CancellationTokenSource into StepContext

NBomber v3.2.1

NBomber

• Fixed issue with disposing CancellationTokenSource
• Migrated to new Serilog.Sinks.SpectreConsole Version="[0.3.3]"

NBomber v3.2.0

NBomber

• Added live status table for console

NBomber v3.1.0

• Fixed issue with missed C# API Step.Create overload
• Fixed minor console bug with rendering progress bar for warm up when it jumped before starting bombing
• Added functionality to stop test execution when too many fails
• Refactored scheduling scenarios to use one single timer
• Changed default step timeout from 1 sec to 5 sec
• Cosmetic changes for console progress bar

NBomber v3.0.0-rc2

NBomber

• Extended logs with info: NodeType, ClusterId, AgentGroup
• Fixed bug with incorrect parsing of duration that more than 24h - the duration format is "d:hh:mm:ss", for example, to specify test duration 25h will be "1:01:00:00"
• Improved ProgressBar - it nows display [00:01:05] - [00:03:00] (elapsed time - final duration time), also rendering speed was decreased to use less resources

NBomber.Sinks.InfluxDB

• Added session_id, node_current_operation

NBomber.Grafana

• Demo of new dashboards
• Added a new Sessions Dashboard
• Added a new NBomber Dashboard

NBomber v3.0.0-RC

NBomber

Removed Newtonsoft Json
Fixed bug with not correct LoadSimulationStats when Agent is overloaded

NBomber v3.0.0-beta.12

NBomber

• Fixed bug with NRE when Coordinator is having empty TargetScenarios
• Moved PushExtensions to NBomber.Push

NBomber v3.0.0-beta.11

NBomber

• Added TestInfo.ClusterId
• Renamed StepContext.InvocationCount -> InvocationNumber
• Refactored RealtimeStats (improved performance for cluster with many agents)

NBomber.Sinks.InfluxDB

• Added "cluster_id" tag and "cluster_node" metric point

NBomber.Cluster

• Added optional config setting MinAgentsCount for the Coordinator JSON config file. It allows setting a minimum count of agents that the coordinator will wait to start the session

    "ClusterSettings": {
        "Coordinator": {
            "ClusterId": "test_cluster",
            "NATSServerURL": "nats://localhost",
            "TargetScenarios": ["test_scenario"],
            "Agents": [
                { "AgentGroup": "1", "TargetScenarios": ["test_scenario"] }
            ],
            "MinAgentsCount": 5
        }
    }

• Added functionality to load JSON configuration by HTTP URL

let url = "http://config.com/json_file_path"

Scenario.create "scenario_1" [step1; step2]
|> NBomberClusterRunner.registerScenario
|> NBomberClusterRunner.loadConfig url

v3.0.0-beta.10

NBomber

• Added DefaultStepTimeoutMs on configuration level
• New API NBomberRunner.WithDefaultStepTimeout(TimeSpan)
• New Config JSON setting DefaultStepTimeoutMs
• Renamed DisableHintsAnalyzer() to EnableHintsAnalyzer(true | false)
• Added StepContext.ScenarioInfo.ScenarioOperation
• Improved CSV report by @mrBoie
• Improved displaying scenarios with WarmUp: on WarmUp, the console shows only scenarios that contain WarmUpDuration

NBomber Cluster

• Added MsgPack serialization + LZ4 compression for streaming stats from Agents

• Fixed NBomber scenario stats showing incorrect ramp_constant, instead of the configured inject_per_sec

• Increased default timeout to discover all available agents, it's now = 5 sec

• Fixed bug with displaying and waiting on WarmUp for scenario started only on Agent

• Added ability to run coordinator without any scenarios to balance the load for a coordinator in the cluster with many agents and very load intensive scenarios. For this you should set empty array "TargetScenarios": []

    "ClusterSettings": {
        "Coordinator": {
            "ClusterId": "test_cluster",
            "NATSServerURL": "my-nats",
            "TargetScenarios": [],
            "Agents": [
                { "AgentGroup": "1", "TargetScenarios": ["scenario_2"] }
            ]
        }
    },