ByteBlower Endpoints used to go into "Silent Mode" while a test scenario was running. Not anymore! You can now configure the scenario heartbeat interval, and maintain connectivity with each Wireless Endpoint:

This new feature will allow you to cancel a test without needing to stop the BEP app manually. This is very useful when working remotely and executing longer test durations!

Changelog 2.19.2

Changes

macOS uses the external browser for showing reports. This approach is a work-around to avoid incompatibilities between macOS Ventura and the UI platform.
The ByteBlower GUI stays fixed in a light appearance for the macOS Dark Mode. This avoids unreadable text due to color mismatches when the system switches to a dark appearance. This update requires reinstalling the ByteBlower GUI, however, all settings and reports are saved.

Changelog 2.19.0

Enhancements

Added more TCP Roundtrip statistics in the HTML, CSV and JSON report. New values include the average latency and Time To First Byte (TTFB). More information about these metrics is on our support website.
The GUI has more accurate TCP graphs by using the average TCP RTT instead of a sampled value.
The size of the FrameBlasting frame can now be changed immediately from the size column at the left side of the Frame View.
To make it easier to get started immediately, ByteBlower Systems are now refreshed on startup. This happens in the background.
Small UI improvements in the Frame Blasting View to make it more visible where to edit the FrameBlasting settings.
You can now immediately start a PCAP capture when launching a test-run.
Tests with Wireless Endpoints are now cancelable using the GUI. No need to push the "Abort" button anymore on each Wireless Endpoint.
The CLT return values have been updated and documented.
In the report graphs, the RSSI axis does not show decimals anymore.
RSSI information has been added to the CSV report.
The GUI became unresponsive when setting big Frame Repeat values.

Bug fixes

JSON reports of tests canceled during the configuration phase had a nullpointer exception in the background.

ByteBlower Server 2.19 changelog

Server 2.19.0 (20/10/2022)

Highlights

The ByteBlower MeetingPoint now supports stopping a ByteBlower Endpoint from the ByteBlower API or ByteBlower GUI.
This feature allows the user to stop a ByteBlower Endpoint app in a way it was already possible with a classic ByteBlower Port.

New Features

Adding support for ByteBlower Endpoints who keep communicating during the test.
Adding support to stop a ByteBlower Endpoint during the test. In order for this feature to work, the ByteBlower API or ByteBlower GUI must be configured so the ByteBlower Endpoint keeps communicating during the test. This feature requires a ByteBlower API or ByteBlower GUI updated to version 2.19.0 or higher and a ByteBlower Endpoint running at least 2.19.0.

Improvements

Adding iPadOS 15 as a supported platform.
Note: In order not to break existing scripts, iPadOS is announced as iOS towards the customer.

Fixes

The ByteBlower MeetingPoint could crash when a ByteBlower API disconnected when a ByteBlower Endpoint was executing specific API calls.
These calls are used when:
- Preparing a ByteBlower Endpoint for test execution
- Starting a test on a ByteBlower Endpoint
- Gathering results for an executed test.

Misc

The ByteBlower 5100 Linux kernel is updated from Debian version 4.19.0-18 to 2.19.0-21
The ByteBlower 3100 and ByteBlower 3200 server network interface drivers are updated so they don't lose network connectivity under high traffic loads.
The ByteBlower 5100 system can now update the firmware for the used traffic interfaces.

ByteBlower API 2.19 Changelog

Changelog 2.19.0 (20/10/2022)

Download

You can download the latest version at https://setup.byteblower.com/software.html.

Enhancements

The API now allows the user to configure continuous communication between the ByteBlower Endpoint and ByteBlower MeetingPoint. Therefore 2 new methods are added to the WirelessEndpoint object:
- ScenarioHeartbeatIntervalGet() which allows to read the currently configured Scenario Heartbeat interval.
- ScenarioHeartbeatIntervalSet(nanoseconds) which allows to set the interval on which the ByteBlower Endpoint should try to communicate with the ByteBlower MeetingPoint.
  A value of 0 disables continuous communication between the ByteBlower Endpoint and the ByteBlower MeetingPoint, which is the behaviour as per pre 2.19.0.
The API can now stop a running test on the ByteBlower Endpoint.
Therefore one new method is added to the WirelessEndpoint object:
- Stop().
  In order for this feature to work, the ScenarioHeartbeatInterval parameter must be set to a value other than 0 (disabled) and the ByteBlower Endpoint and ByteBlower MeetingPoint must be running software version 2.19.0 or higher.

Fixes

The ByteBlower TCL API did not have Scenario.Duration.Set method available on the WirelessEndpoint object.

ByteBlower GUI 2.18 changelog

Bigger, longer tests using Dashboards

Monitoring live test-results is a large benefit to endurance tests. This version of the ByteBlower GUI makes the results of the Realtime view available for other dedicated tools like Prometheus and Grafana. This allows you to

Run longer tests, including multi-day test runs.
Add more flows to a scenario since many of the CPU-intensive tasks are delegated to dedicated tools