ByteBlower GUI 2.19.0
Cancelable ByteBlower Endpoints
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!
- 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.
- 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.
- JSON reports of tests canceled during the configuration phase had a nullpointer exception in the background.