#testing #test-server #nats #server

bin+lib nats_test_server

An intentionally buggy NATS server that facilitates fault injection for testing error paths in NATS-based libraries

5 unstable releases

0.3.0 Feb 8, 2021
0.2.0 Nov 23, 2020
0.1.2 Jul 6, 2020
0.1.1 Jul 6, 2020
0.1.0 Jun 29, 2020

#37 in #test

Download history 9/week @ 2024-12-26 343/week @ 2025-01-02 146/week @ 2025-01-09 256/week @ 2025-01-16 182/week @ 2025-01-23 220/week @ 2025-01-30 240/week @ 2025-02-06 283/week @ 2025-02-13 226/week @ 2025-02-20 448/week @ 2025-02-27 413/week @ 2025-03-06 320/week @ 2025-03-13 249/week @ 2025-03-20 246/week @ 2025-03-27 359/week @ 2025-04-03 314/week @ 2025-04-10

1,252 downloads per month

Apache-2.0

24KB
566 lines

Test server

A test NATS server for testing the NATS rust client and applications using it. Allows injection of bugsand useful for testing a number of things.

Example usage

#[test]
fn test_use_nats() {
  let nats = NatsTestServer::build().spawn();

  let my_component1 = component(nats.address())
  let my_component2 = component(nats.address())

  // test component behaviour

  let nats = nats.restart().spawn();

  // test behaviour after restart
} // server is stopped on drop

#[test]
fn test_use_buggy_nats() {
  let nats = NatsTestServer::build().bugginess(400).spawn(); // a 1/400 chance of restarting on any given message

  // bugginess test
}

Limitations

  • hop_ports doesn't make any sense for multiple clients

Dependencies

~5–13MB
~153K SLoC