testing TTCN3 test stability

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/.

Mirko Kovacevic northmirko at gmail.com
Sat Feb 13 18:27:34 UTC 2021


Harald/Osmocom team gave TTCN3 real meaning and public attention. Before
you came up, TTCN3 was a prisoner of worthless, dry academic papers.

On Sat, 13 Feb 2021, 18:08 Harald Welte, <laforge at osmocom.org> wrote:

> I think this might be of interest to some of the other developers.
>
> Soemtimes we have a problem that the test suite itself is not 100% stable,
> and it's not easy to reproduce a test that fails sporadically every Nth
> time.
>
> As the "execute" statement in the "control" section actually returns a
> verdict
> type, you can use the following construct in a control section:
>
> control {
>        for (var integer i := 0; i < 10000; i := i+1) {
>                var verdicttype v;
>                v := execute( TC_paging_ps_ptp_lac() );
>                if (v != pass) {
>                        break;
>                }
>        }
> }
>
> This way you keep running the test suite until the given test fails for
> the first time.  Then go do something else for some hour(s) and by the
> time you get back, hopefully you will have reproduced the problem.
>
> Regards,
>         Harald
> --
> - Harald Welte <laforge at osmocom.org>
> http://laforge.gnumonks.org/
>
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
>                                                   (ETSI EN 300 175-7 Ch.
> A6)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210213/7227d880/attachment.htm>


More information about the OpenBSC mailing list