From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.6
Path: eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.ada
Subject: Re: Ada and software testing
Date: Fri, 16 Jul 2021 03:21:24 -0700
Organization: A noiseless patient Spider
Message-ID: <87pmvi36fv.fsf@nightsong.com>
References: <871r84cq4r.fsf@nightsong.com> <scrlec$h26$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org; posting-host="8751defb0216f199d7787b29733bb2c2";
	logging-data="26258"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX186jxD0fbhRfZrB2MW+gESD"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
Cancel-Lock: sha1:zOEQoBy6RvFb0bl31tP+geEOXWI=
	sha1:46YxRNAbAS3NOXnO3eVs8WDpGhw=
Xref: reader02.eternal-september.org comp.lang.ada:62398
List-Id: <comp.lang.ada>

"G.B." <bauhaus@notmyhomepage.invalid> writes:
> So, what is a proper testing strategy once the programmers have found
> that the transitive closure of some call might sometimes incur externally
> caused behavior? Such as timeout, or ordering effect due to concurrency?

Depending on the situation, this may be an area to try model checking.
I've been wanting to try Alloy (alloytools.org) but so far have only
clicked around its web site a little.  It looks interesting.