qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] How to use qtest


From: Gonglei (Arei)
Subject: Re: [Qemu-devel] How to use qtest
Date: Wed, 14 May 2014 09:26:35 +0000

Hi, Andreas

> -----Original Message-----
> From: Andreas Färber [mailto:address@hidden
> Sent: Wednesday, May 14, 2014 5:06 PM
> To: Gonglei (Arei)
> Cc: Markus Armbruster; address@hidden
> Subject: Re: [Qemu-devel] How to use qtest
> 
> Hi,
> 
> Am 14.05.2014 09:50, schrieb Gonglei (Arei):
> >> -----Original Message-----
> >> From: Markus Armbruster [mailto:address@hidden
> >> Sent: Wednesday, May 14, 2014 3:34 PM
> >> To: Gonglei (Arei)
> >> Cc: address@hidden; Andreas Färber
> >> Subject: Re: [Qemu-devel] How to use qtest
> >>
> >> "Gonglei (Arei)" <address@hidden> writes:
> >>
> >>> I know qemu has a test framework, and I get some information
> >>> from http://wiki.qemu.org/Features/QTest
> >>>
> >>> Recently I want to use qtest for some modules, but I have no idea
> >>> how to run those tests. Such as tests/ e1000-test
> >>>
> >>> Any guidance? Or how to? Thanks in advance!
> >>
> >> Try "make check-help".
> >
> > Thanks!
> > Is there two steps for qtest?
> > First, "make check" for running tests,
> > Second, make "check-report.html" for getting results.
> 
> No, "make check V=1" shows you the progress as well. The HTML or XML
> reports are only necessary for some more verbose info/warning messages
> and for automated reporting purposes.
> 
Good. Thanks!

> > If I want to write some qtest by myself, any guidance? Thanks.
> 
> Use out-of-tree builds. One for your regular development and testing,
> one for gcov coverage testing. The latter (--enable-gcov) will dump
> statistics about test coverage and allow you to verify you got the paths
> for new tests right (it's not the source code paths but the paths to the
> .o files actually, with target-i386 as placeholder for target-*).
> 
> There's a lot of stubs that I've been adding recently that you can copy
> (see git history for how to add them to Makefile); for functional tests
> see libqtest.h and the libqos/ subdirectory and grep for existing tests
> that use those functions. 
>
Okay, I have noticed that patch sets you pulled.

>More concrete questions will be easier to answer. :)
> 
Yep. Thank you so much!


Best regards,
-Gonglei



reply via email to

[Prev in Thread] Current Thread [Next in Thread]