-
-
Notifications
You must be signed in to change notification settings - Fork 568
Unit Tests
Kyle Reed edited this page May 22, 2023
·
1 revision
cmake --build . --target build_tests && ctest --output-on-failure
- Unit tests are written using the doctest framework.
- Tests are separated into application and baseband depending on which core is targeted.
- Test source is found under
firmware/test/
. - Tests are not currently integrated with the PR pipeline.
- Tests are not currently built as part of a normal build and must be built manually.
In your CMake build directory run cmake --build . --target build_tests
which will build both application and baseband test hosts.
Once tests are built, from your CMake build directory run ctest --output-on-failure
.
Note
The wiki is incomplete. Please add content and collaborate.
Important
- This is a public wiki. Everything is visible to everyone. Don't use it for personal notes.
- Avoid linking to external tutorials/articles; they may become outdated or contain false information.
How to collaborate
How to ask questions correctly
- First steps
- Usage cautions
- Intended use and Legality
- Features
- PortaPack Versions (which one to buy)
- HackRF Versions
- Firmware update procedure
- Description of the hardware
- User interface
- Powering the PortaPack
- Troubleshooting
- Applications
-
Compilation of the firmware
- Compile on WSL with ninja
- How to compile on Windows faster with WSL 2
- Using Docker and Kitematic
- Docker command-line reference
- Using Buddyworks and other CI platforms
- Notes for Buddy.Works (and other CI platforms)
- Using ARM on Debian host
- All in one script for ARM on Debian host
- Compile on Arch based distro (exclude Asahi)
- Dev build versions
- Notes About ccache
- Create a custom map
- Code formatting
- PR process
- Description of the Structure
- Software Dev Guides
- Tools
- Research
- UI Screenshots
- Maintaining
- Creating a prod/stable release (Maintainers only)
- Maintaining rules
- Development States Notes