>Test writers can use their own methods to do this on most DUTs, 

I don't know how test writers to do.
Maybe I didn¡¯t express it clearly. I mean when each case in job is finished(not all cases finished),user program can receive notifications(through the xml-rpc notification mechanism).

At 2018-09-21 00:28:11, "Neil Williams" <neil.williams@linaro.org> wrote:
>On Thu, 20 Sep 2018 at 09:37, john zhang <laojianghusz@163.com> wrote:
>>
>> Lava xml-rpc notification  machnism, criteria.status indicates which event can be notified to user (by hook callback). But the criteria.status only has such as "Complete Incomplete,Canceled,finished" events. Why the lava is not designed a machnism that  notify user when only a test case is complete(err..),if so that user has more rights to control test process execution.
>
>Test writers can use their own methods to do this on most DUTs, e.g.
>if the DUT raises a usable network interface, using curl or any tool
>which can installed on the DUT or in an LXC.
>
>Test writers can also use the lava-test-event helper along with
>lavacli. Documentation and examples of this are pending. See
>https://git.lavasoftware.org/lava/lavacli/issues/1
>https://staging.validation.linaro.org/scheduler/job/239410#L59
>
>The problem is to avoid flooding the user with events because test
>jobs produce a large number of test cases. Note also that results are
>reported in real time.
>
>-- 
>
>Neil Williams
>=============
>neil.williams@linaro.org
>http://www.linux.codehelp.co.uk/