You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jchauncey I'm not sure how i feel about exposing an interface in go-nsq for testing, but I've used this to much success https://gist.github.com/jehiah/572be9b20c55e5ebbd2d21c73da5b08e It might be sufficient for your needs too. The included NoOpMessageDelegate can make it easier to construct nsq.Message for calling a handler directly to test consumers.
So what i wanted to do was test the consumption of a mock message in an app I was writing without having to actually start nsq. I ended up copying a lot of the functions in mock_test to get it to work but that seemed rather clunky.
The code in mock_test feels like too much to be exporting, mostly because it's designed to validate low level protocol behaviors.
I feel like what you want could be much simpler, and depending on what we came up with I think we could at least consider providing as a set of exported types in go-nsq.
Activity
jchauncey commentedon Jun 13, 2016
Basically I'd like to have some of these methods made public - https://github.com/nsqio/go-nsq/blob/master/mock_test.go
jehiah commentedon Jun 13, 2016
@jchauncey I'm not sure how i feel about exposing an interface in go-nsq for testing, but I've used this to much success https://gist.github.com/jehiah/572be9b20c55e5ebbd2d21c73da5b08e It might be sufficient for your needs too. The included
NoOpMessageDelegate
can make it easier to constructnsq.Message
for calling a handler directly to test consumers.jchauncey commentedon Jun 21, 2016
So what i wanted to do was test the consumption of a mock message in an app I was writing without having to actually start nsq. I ended up copying a lot of the functions in
mock_test
to get it to work but that seemed rather clunky.[-]Ability to mock producer/consumer interaction[/-][+]producer/consumer: ability to mock for tests[/+]mreiferson commentedon Jun 25, 2016
The code in
mock_test
feels like too much to be exporting, mostly because it's designed to validate low level protocol behaviors.I feel like what you want could be much simpler, and depending on what we came up with I think we could at least consider providing as a set of exported types in
go-nsq
.Are you interested in taking a pass?
mreiferson commentedon Apr 16, 2017
See #146
sefasenturk95 commentedon Mar 7, 2018
Is it still not possible to mock NSQ?