When debugging device-related issues, there is a need to run the device-related tests as quickly as possible, without running the regular tests at first. Instead of commenting the scripts in the run_tests.sh to do that, the device-related tests should be isolated in a standalone test script. Then it's easier to run those tests by a command like sh run_device_tests.sh. In addition, it can be run with other available flags together, such as RUSTFLAGS="-Z sanitizer=*" or RUST_BACKTRACE=full.
Within this change, the README is also updated to reflect the usage of the current tests. It helps the readers to know how to test the library in different ways.
When debugging device-related issues, there is a need to run the device-related tests as quickly as possible, without running the regular tests at first. Instead of commenting the scripts in the run_tests.sh to do that, the device-related tests should be isolated in a standalone test script. Then it's easier to run those tests by a command like
sh run_device_tests.sh
. In addition, it can be run with other available flags together, such asRUSTFLAGS="-Z sanitizer=*"
orRUST_BACKTRACE=full
.Within this change, the README is also updated to reflect the usage of the current tests. It helps the readers to know how to test the library in different ways.