Files
nats-server/server
Neil 59bc094e86 [FIXED] Increased AckWait in TestMQTTQoS2RetriesPublish, TestMQTTQoS2RetriesPubRel (#4518)
TestMQTTQoS2RetriesPublish to 100ms, and in TestMQTTQoS2RetriesPubRel to
50ms.

A lesser value caused another PUBLISH to be fired while the test was
still processing the final QoS2 flow. Reduced the number of retries we
wait for to make the test a little quicker.
2023-09-13 11:49:17 +01:00
..
2023-08-02 11:25:48 -07:00
2023-07-18 12:21:31 -07:00
2023-06-03 10:03:23 +05:30
2023-06-05 14:13:18 -07:00
2023-09-12 15:52:00 -07:00
2023-09-01 11:19:33 -07:00
2023-08-21 15:55:31 -07:00
2023-06-27 20:41:57 -07:00
2023-06-02 13:19:22 +03:00
2023-09-12 07:52:17 -07:00
2023-08-21 15:55:00 -07:00
2023-08-31 15:52:00 -07:00
2023-07-21 16:56:13 -07:00
2023-07-21 16:56:13 -07:00
2023-09-05 14:39:28 -07:00
2023-09-12 17:19:30 -07:00
2023-08-30 14:54:30 -07:00
2023-08-02 11:25:48 -07:00
2023-08-04 10:15:35 -07:00
2023-04-12 11:48:22 -07:00
2023-04-12 11:48:22 -07:00
2023-08-25 11:03:54 -07:00
2023-08-02 11:25:48 -07:00
2023-09-04 16:54:36 +01:00
2023-04-29 19:52:57 -07:00
2023-09-11 21:12:15 -07:00
2023-08-01 21:46:54 -07: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.