You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bladeRF firmware (FX3 and FPGA) are not that simple. We should develop a standard test-suite to verify functionality. I have started drafting notes on what it should cover https://github.com/Nuand/bladeRF/wiki/Release-testing . As I have been focusing on flashing and now USB spec compliance, I have listed tests that come to mind with those are in focus. However there should be additional tests that covers:
There will also need to be tests for exposed external API's, like osmosdr and eventually extio.dll.
Ideally these tests will be fully automated and linked to build outputs. The cross platform aspect of the testing will require testing machines on target platforms with dedicated attached hardware.
The text was updated successfully, but these errors were encountered:
The bladeRF firmware (FX3 and FPGA) are not that simple. We should develop a standard test-suite to verify functionality. I have started drafting notes on what it should cover https://github.com/Nuand/bladeRF/wiki/Release-testing . As I have been focusing on flashing and now USB spec compliance, I have listed tests that come to mind with those are in focus. However there should be additional tests that covers:
There will also need to be tests for exposed external API's, like osmosdr and eventually extio.dll.
Ideally these tests will be fully automated and linked to build outputs. The cross platform aspect of the testing will require testing machines on target platforms with dedicated attached hardware.
The text was updated successfully, but these errors were encountered: