How do you run Monero's automated tests?
Automated tests are essential for ensuring that code changes haven't introduced bugs.
Quick Answer
Monero includes an integrated test suite that can be executed after compilation using the 'make release-test' command within your build environment. These tests perform checks on core consensus rules, cryptographic functions, and networking logic to ensure the integrity of the binary you have produced.
Ensuring Reliability
Running tests after compiling is the best way to catch errors specific to your system or configuration. It ensures that the cryptographic foundations of the code are performing as expected on your hardware.
Given the importance of Monero's consensus rules, these tests play a vital role in maintaining the security and stability of your local node.
The Testing Process
Note that some core tests can be extensive and may take several hours to complete. Be prepared for your CPU to be under load during the entire duration of the test suite.
If any test fails, review the output logs to identify the cause. Do not use a binary that fails the test suite for any production environment.
Sources
Related reading
Key takeaways
- Run 'make release-test' after compilation.
- Tests ensure core protocol integrity and stability.
