Files
nats-server/server
Ivan Kozlovic b32d6b4e44 Fixed callout tests that were not doing cleanup causing data races
Because of the lack of `defer ac.Cleanup()` in some tests, the
accounts would still try to send conn updates, which was possibly
causing data races with some of the tests that change the
eventsHBInterval global variable.

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
2023-04-03 09:32:28 -06:00
..
2023-02-10 10:29:26 +00:00
2023-01-27 08:35:59 -08:00
2022-07-05 09:33:12 +01:00
2022-09-08 11:28:23 -06:00
2023-04-02 18:58:54 -07:00
2022-07-05 09:28:00 +01:00
2023-04-03 09:32:28 -06:00
2022-11-14 08:28:19 -08:00
2023-03-31 23:55:50 +02:00
2023-02-28 15:17:24 -08:00
2022-12-13 13:08:35 -08:00
2023-02-10 10:29:26 +00:00
2023-02-10 10:29:26 +00:00
2023-04-03 09:32:28 -06:00
2023-04-03 09:32:28 -06:00
2023-01-17 17:40:39 -08:00
2022-12-27 09:41:39 +01:00
2023-02-10 10:29:26 +00:00
2022-07-05 09:33:12 +01:00
2022-07-05 09:28:00 +01:00
2023-04-02 18:58:54 -07:00
2022-03-25 12:11:55 -06:00

Tests

Tests that run on Travis have been split into jobs that run in their own VM in parallel. This reduces the overall running time but also is allowing recycling of a job when we get a flapper as opposed to have to recycle the whole test suite.

JetStream Tests

For JetStream tests, we need to observe a naming convention so that no tests are omitted when running on Travis.

The script runTestsOnTravis.sh will run a given job based on the definition found in ".travis.yml".

As for the naming convention:

  • All JetStream tests name should start with TestJetStream
  • Cluster tests should go into jetstream_cluster_test.go and start with TestJetStreamCluster
  • Super-cluster tests should go into jetstream_super_cluster_test.go and start with TestJetStreamSuperCluster

Not following this convention means that some tests may not be executed on Travis.