14 Jan
2014
14 Jan
'14
9:54 a.m.
On 13.01.2014 09:52, Holger Hans Peter Freyther wrote:
On Tue, Jan 07, 2014 at 12:07:45PM +0100, Jacob
Erlbeck wrote:
Hmm, that's unit testing mainly targeted at the MGCP parser. So I'm not
too concerned about that, as long as I keep away from the part of the
state that is really used by the parser and not only set as a side effect.
+ endp->bts_end.output_enabled = 0;
+ endp->net_end.output_enabled = 0;
I am afraid that with the manipulation of internal state
we move away from testing the real thing. I understand that you want to capture the effect of
parsing the
message once. What about assigning variables that are not within the
scope of what libmgcp/ would normally use? This way we can be sure
that a.) libmgcp set these variables and b.) they are what we wanted
it to be set to?
That would be ok, what's about 42 or -1?
Jacob