Pre Release Checklist

Things to test before publishing a new release. Those are mainly things that are hard/impossible to catch via automated testing because they actually need the real hardware to run on.

General

• Check that a hint about supported browsers is shown in Firefox
• Check that a hint about supported browsers is shown in Brave
• Check that Browser information is shown in the logs
• Clear application cache in browser
• Check that language is automatically detected
• Make sure cookie banner is displayed
• Make sure language selection is saved between reloads
• Make sure cookie banner is not displayed after accepting

BLHeli_S based (H & X)

• Flash latest version of BLHeli_S (as a Baseline for testing)
• Flash Bluejay via Dropdown (latest stable version)
• Change settings - write, read, disconnect, read again
• Flash different version of Bluejay, make sure settings are migrated
• Flash a single ESC > 1. Make sure information is updated accordingly
• Make sure melody editor is playing melodies and highlighting notes properly
• Change melody to a long melody, disconnect
• Make sure reading fails with a proper error message while melody is playing
• Make sure reading settings works after melody finishes playing
• Enable pre-releases in settings, make sure that pre-releases are shown (if applicable)
• Flash pre-release (if applicable)
• Check that blacklisted versions are not available for flashing (<=0.8)
• Flash a local version of Bluejay
• Make sure that it is not possible to flash a wrong layout
• Make sure no settings are migrated from Bluejay
• Disable common settings
• Change common settings
• Enable common settings and make sure common settings are shown out of sync
• Restore default settings
• Flash mistagged BlHeli_S firmware and make sure that it is recognized as such
• Check mistagged error message when selecting image to flash
• Check that battery voltage is shown
• Spin up all motors
• Spin up a single motor
• Verify that motors stop spinning when disconnecting via button
• Check that sliders are working
• Enable advanced settings
• Verify that dumping firmware is possible (resulting in a hex file)
• Change settings / flash different Bluejay version
• Flash back the previously dumped hex file
• Verify that an ESC with the "FLASH*FAILED" status is still shown in the listing and can be recovered
• Verify that L Type MCUs are not detected as mistagged with BLHeli_S flashed
• Verify that JESC is properly detected and an unsupported message is shown

AM32

• Verify that settings can be read
• Check that blacklisted versions are not available for flashing
• Flash oldest available firmware
• Check that settings can be changed and saved
• Check that restoring the default settings works
• Flash latest bootloader updater
• Make sure hint is shown to flash the firmware (TODO)
• Enable pre-releases
• Flash latest firmware
• Check that melody editor is enabled
• Check that melody is playing
• Check that a different melody can be written
• Check that settings can be changed and saved
• Verify that dumping firmware is possible
• Check that battery voltage is shown
• Spin up all motors
• Spin up a single motor
• Check that sliders are working
• Read with latest offline tool
• Check that the settings match what was set with esc-configurator
• Write settings with offline tool
• Check that settings match with what was written with the offline tool

Maintenance

• Create new release branch
• Check that changelog contains all major changes
• Bump all version numbers
• Run test suit for a last time
• Publish release
• Check on prod