[PATCH 3/9] mgcp/test: Test the connection mode parser

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Holger Hans Peter Freyther holger at freyther.de
Mon Jan 13 08:52:50 UTC 2014


On Tue, Jan 07, 2014 at 12:07:45PM +0100, Jacob Erlbeck wrote:

> +		endp->bts_end.output_enabled = 0;
> +		endp->net_end.output_enabled = 0;

> +			endp->bts_end.output_enabled = 0;
> +			endp->net_end.output_enabled = 0;

> +Connection mode: 1, BTS output disabled, NET output disabled

It is the third time I try to write something but I don't find the
right words. 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?

holger




More information about the OpenBSC mailing list