[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180309.112229.636378484047728382.davem@davemloft.net>
Date: Fri, 09 Mar 2018 11:22:29 -0500 (EST)
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, batuhanosmantaskaya@...il.com,
dcaratti@...hat.com, netdev@...r.kernel.org, kernel@...atatu.com
Subject: Re: [PATCH v2 net-next] tools: tc-testing: Can refer to $TESTID in
test spec
From: "Brenda J. Butler" <bjb@...atatu.com>
Date: Thu, 8 Mar 2018 15:27:44 -0500
> When processing the commands in the test cases, substitute
> the test id for $TESTID. This helps to make more flexible
> tests. For example, the testid can be given as a command
> line argument.
>
> As an example, if we wish to save the test output to a file
> named for the test case, we can write in the test case:
>
> "cmdUnderTest": "some test command | tee -a $TESTID.out"
>
> Signed-off-by: Brenda J. Butler <bjb@...atatu.com>
Applied.
Powered by blists - more mailing lists