#nats #injection #testing #fault #nats-client #facilitate #test-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

#11 in #fault

Download history 285/week @ 2024-11-16 227/week @ 2024-11-23 174/week @ 2024-11-30 184/week @ 2024-12-07 270/week @ 2024-12-14 19/week @ 2024-12-21 184/week @ 2024-12-28 201/week @ 2025-01-04 214/week @ 2025-01-11 195/week @ 2025-01-18 232/week @ 2025-01-25 238/week @ 2025-02-01 227/week @ 2025-02-08 278/week @ 2025-02-15 211/week @ 2025-02-22 574/week @ 2025-03-01

1,330 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–14MB
~154K SLoC