Files
nats-server/server
Pierre Mdawar 6d6d3cfa55 Fix Content-Type header in /healthz when status is not 200 OK (#4437)
- Added a new internal function `handleResponse` that accepts the HTTP 
  status code and sets it after setting the headers
- Added tests for the `/healthz` endpoint for the `ok`, `error` and `unavailable` statuses
- Changed the IETF API health check URL to 
https://datatracker.ietf.org/doc/html/draft-inadarei-api-health-check

Resolves #4436
2023-08-31 13:55:20 -07:00
..
2023-08-02 11:25:48 -07:00
2023-01-27 10:43:30 +08:00
2023-06-05 13:02:05 -07:00
2023-08-31 08:33:22 -07:00
2023-08-21 22:03:26 +01:00
2023-08-21 22:03:26 +01:00
2023-08-31 08:59:15 -07:00
2022-11-14 08:28:19 -08:00
2023-06-02 13:19:22 +03:00
2023-07-21 16:56:13 -07:00
2023-07-21 16:56:13 -07:00
2023-08-30 14:54:30 -07:00
2023-08-02 11:25:48 -07:00
2023-03-30 15:02:59 -06:00
2023-04-12 11:48:22 -07:00
2023-04-12 11:48:22 -07:00
2023-08-02 08:51:08 -07:00
2023-08-02 11:25:48 -07:00
2023-06-05 22:41:09 +03:00
2023-07-21 16:56:13 -07:00
2023-08-17 15:28:48 +01: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.