Skip to content

TESTING.md

Latest commit

 

History

History
35 lines (25 loc) · 1.15 KB

TESTING.md

File metadata and controls

35 lines (25 loc) · 1.15 KB

How to test serialport-rs for development.

Without hardware:

  1. Compilation
  2. cargo test

With a single unconnected device:

cargo run --example hardware_check <DEVICE>

And when wired in a physical loopback mode:

cargo run --example hardware_check <DEVICE> --loopback

With two devices connected to each other:

  • cargo run --example hardware_check <DEVICE1> --loopback-port <DEVICE2>
  • Also cargo run --example heartbeat <DEVICE1> <BAUD> in one terminal and cargo run --example receive_data <DEVICE2> <BAUD> in another
  • Running tests with test cases requiring hardware devices enabled: 
    $ export SERIALPORT_TEST_PORT_1=$(realpath /dev/ttyX)
$ export SERIALPORT_TEST_PORT_2=$(realpath /dev/ttyY)
$ cargo test --features hardware-tests
  • Please use the /dev/cu.* flavor of a serial device on macOS as the file locking tests seem to block with the /dev/tty.* flavor

Can also verify trickier settings (like non-standard baud rates) using serial terminal programs like: