get.pme.sh/pnats@v0.0.0-20240304004023-26bb5a137ed0/server/README.md (about)

     1  # Tests
     2  
     3  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.
     4  
     5  ## JetStream Tests
     6  
     7  For JetStream tests, we need to observe a naming convention so that no tests are omitted when running on Travis.
     8  
     9  The script `runTestsOnTravis.sh` will run a given job based on the definition found in "`.travis.yml`".
    10  
    11  As for the naming convention:
    12  
    13  - All JetStream tests name should start with `TestJetStream`
    14  - Cluster tests should go into `jetstream_cluster_test.go` and start with `TestJetStreamCluster`
    15  - Super-cluster tests should go into `jetstream_super_cluster_test.go` and start with `TestJetStreamSuperCluster`
    16  
    17  Not following this convention means that some tests may not be executed on Travis.