[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20171101.110531.994137137362345579.davem@davemloft.net>
Date: Wed, 01 Nov 2017 11:05:31 +0900 (KST)
From: David Miller <davem@...emloft.net>
To: bjb@...atatu.com
Cc: jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us,
chrism@...lanox.com, lucasb@...atatu.com, aring@...atatu.com,
mrv@...atatu.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] tc-testing: very simple example test cases
From: "Brenda J. Butler" <bjb@...atatu.com>
Date: Tue, 31 Oct 2017 14:25:46 -0400
> As part of documentation, supply some very simple test cases
> to illustrate how test cases work. One test case shows
> commands in the setup, command, verify and teardown stages.
> Other test cases show how to have a working test case that
> does not have commands in the setup, verify and/or teardown
> stages.
>
> Specifically, the command lists for setup and teardown can
> be empty. And the verify command must have a command, but
> it can be /bin/true. The regex must have a string, we
> recommend a single space, and the count of matches must be
> zero if you do not want to use the match feature of verify.
> Verify will always look for a return code of success (0)
> so we give /bin/true when we do not want to make a check
> there.
>
> Also, update the documentation for testcases to be more
> specific in the cases of:
>
> - accepting non-success return codes in setup and
> teardown stages
> - how to write the test when no setup, teardown
> and/or verify are desired.
>
> To run the example test cases:
...
> Signed-off-by: Brenda J. Butler <bjb@...atatu.com>
Applied.
Powered by blists - more mailing lists