#nats #testing #injection #test-server #fault-injection #buggy

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

#506 in Text editors

Download history 321/week @ 2025-04-09 180/week @ 2025-04-16 185/week @ 2025-04-23 140/week @ 2025-04-30 188/week @ 2025-05-07 253/week @ 2025-05-14 330/week @ 2025-05-21 285/week @ 2025-05-28 259/week @ 2025-06-04 274/week @ 2025-06-11 303/week @ 2025-06-18 295/week @ 2025-06-25 163/week @ 2025-07-02 254/week @ 2025-07-09 312/week @ 2025-07-16 177/week @ 2025-07-23

940 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

~4–14MB
~151K SLoC