How to organize interruption of infinite loops in tests?

Question

go

I inherited a project written on GO (comet server) and now the task is to cover everything with integration tests.
Comet processes messages from channels (go channels) in an infinite loop, then processes these messages.
In general, how to succinctly organize the interruption of such a cycle in tests after all messages have been processed?

I have only one thought - this is the addition of a new channel, which will be responsible for interrupting the loop, but something like that ...

Answer 1

Close the channel in the test, and the function reading in the message loop should terminate gracefully.
Example:

data, ok := <-channel
if !ok {
    return
}