Files
nats-server/server/service_test.go
Jaime Piña e12181cb83 Return not ready for connection reason
Currently, we use ReadyForConnections in server tests to wait for the
server to be ready. However, when this fails we don't get a clue about
why it failed.

This change adds a new unexported method called readyForConnections that
returns an error describing which check failed. The exported
ReadyForConnections version works exactly as before. The unexported
version gets used in internal tests only.
2021-04-20 11:45:08 -07:00

53 lines
1.2 KiB
Go

// Copyright 2012-2018 The NATS Authors
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
// +build !windows
package server
import (
"testing"
"time"
)
func TestRun(t *testing.T) {
var (
s = New(DefaultOptions())
started = make(chan error, 1)
errC = make(chan error, 1)
)
go func() {
errC <- Run(s)
}()
go func() {
if err := s.readyForConnections(time.Second); err != nil {
started <- err
return
}
s.Shutdown()
close(started)
}()
select {
case err := <-errC:
if err != nil {
t.Fatalf("Unexpected error: %v", err)
}
case <-time.After(2 * time.Second):
t.Fatal("Timed out")
}
if err := <-started; err != nil {
t.Fatalf("Unexpected error: %v", err)
}
}