Starting NATS server in a test

[Henrik Johansson]

Hi,

Is this normally something people do in their apps?

We are starting to get a bit more refined usage of NATS and mocking can get tedious and redundant.

I think it should be fairly easy and my approach is to use default for everything except port.

Does it make sense? Any tips and tricks?

/ Henrik

 

[Colin Sullivan]

Henrik,

We do this in unit tests for our NATS clients.  Check out the links below...

Go 

https://github.com/nats-io/nats/blob/v1.2.0/test/test.go#L79

C# (with AppVeyor)

https://github.com/nats-io/csnats/blob/v0.6.0/NATSUnitTests/UnitTestUtilities.cs#L45

https://github.com/nats-io/csnats/blob/v0.6.0/appveyor.yml#L3

C (with Travis CI)

https://github.com/nats-io/cnats/blob/v1.4.4/.travis.yml#L22

https://github.com/nats-io/cnats/blob/v1.4.4/install_gnatsd.sh

https://github.com/nats-io/cnats/blob/v1.4.4/test/test.c#L2773

Colin

[Henrik Johansson]

Thanks Colin!

I was missing that sneaky loop to wait for the server getting up :)

--
You received this message because you are subscribed to the Google Groups "nats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to natsio+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.