From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Dmitry Monakhov <dmonakhov@openvz.org>,
fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH 2/2] report: Add xunit format report generator
Date: Wed, 8 Mar 2017 11:00:23 +0800 [thread overview]
Message-ID: <20170308030023.GW14226@eguan.usersys.redhat.com> (raw)
In-Reply-To: <CAOQ4uxggR96taZ0Bs3JnNEU-YW6f1QO9t2MDHiThc2DOLHcQ3A@mail.gmail.com>
On Tue, Mar 07, 2017 at 03:13:01PM +0200, Amir Goldstein wrote:
> On Tue, Mar 7, 2017 at 2:05 PM, Eryu Guan <eguan@redhat.com> wrote:
> > On Fri, Mar 03, 2017 at 12:26:16PM +0400, Dmitry Monakhov wrote:
> >> xunit[1]/junit[2] are well known report formats for tests frameworks which
> >> supported by most of test CI frameworks(such as Jenkins [3], Bamboo [4], Avocado [5])
> >> Basically this is just xml document which can be easily parsed later by external tools.
> >>
> >> changes since v2: (in response to eguan@)
> >> - assert repot format on initialization
> >> - Tabify new files
> >>
> >> changes since v1:
> >> - Use generic '-R fmt' option for report generation, asked by eguan@
> >> - localize variables, asked by eguan@
> >> - do not add empty files to report asked by eguan@
> >> - Add properties
> >> - Fix system-err/system-out node nesting
> >>
> >> EXAMPLE:
> >> #./check -R xunit -s ext4 generic/001 generic/010
> >> #cat results/ext4/result.xml
> >> <?xml version="1.0" encoding="UTF-8"?>
> >> <testsuite name="xfstests" errors="0" skipped="1" tests="2" time="7" hostname="alice" timestamp="2017-02-21T15:15:06" >
> >> <properties>
> >> <property name="SECTION" value="ext4"/>
> >> <property name="FSTYP" value="ext4"/>
> >> <property name="MOUNT_OPTIONS" value="-o acl,user_xattr "/>
> >> <property name="HOST_OPTIONS" value="/devel/xfstests-dev.git/configs/alice.config"/>
> >> <property name="XFS_MKFS_OPTIONS" value="-bsize=4096"/>
> >> <property name="TIME_FACTOR" value="1"/>
> >> <property name="LOAD_FACTOR" value="1"/>
> >> <property name="TEST_DIR" value="/mnt/test"/>
> >> <property name="TEST_DEV" value="/dev/ram0"/>
> >> <property name="SCRATCH_DEV" value="/dev/ram1"/>
> >> <property name="SCRATCH_MNT" value="/mnt/scratch"/>
> >> <property name="OVERLAY_UPPER_DIR" value="upper"/>
> >> <property name="OVERLAY_LOWER_DIR" value="lower"/>
> >> <property name="OVERLAY_WORK_DIR" value="work"/>
> >> </properties>
> >> <testcase classname="xfstests.ext4" name="generic/001" time="5">
> >> </testcase>
> >> <testcase classname="xfstests.ext4" name="generic/010" time="1">
> >> <skipped message="src/dbtest not built" />
> >> </testcase>
> >> </testsuite>
> >>
> >> Footnotes:
> >> [1] https://xunit.github.io/docs/format-xml-v2.html
> >> [2] http://help.catchsoftware.com/display/ET/JUnit+Format
> >> [3] https://jenkins.io
> >> [4] https://www.atlassian.com/software/bamboo
> >> [5] https://github.com/avocado-framework/avocado
> >>
> >> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
> >
> > I renamed OVERLAY_{UPPER,LOWER,WORK}_DIR to OVL_{UPPER,LOWER,WORK} in
> > this patch, as they've been updated by recent overlayfs patch.
> >
>
> I would prefer if those were not configuration options at all.
>
> As I wrote in commit 6f5ba68b:
>
> - Make those vars values non-configurable, because lower/upper/work
> directory names are an internal test detail which should
> not concern the user and because we wish to simplify
> and document the overlay tests setup
Thanks for the reminder!
Dmitry, do you mind I removing all these overlay variables from
REPORT_ENV_LIST?
Thanks,
Eryu
next prev parent reply other threads:[~2017-03-08 3:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 8:26 [PATCH 0/2] Add report generators support v3 Dmitry Monakhov
2017-03-03 8:26 ` [PATCH 1/2] check: prepare test report generator infrastructure Dmitry Monakhov
2017-03-03 8:26 ` [PATCH 2/2] report: Add xunit format report generator Dmitry Monakhov
2017-03-07 12:05 ` Eryu Guan
2017-03-07 13:13 ` Amir Goldstein
2017-03-08 3:00 ` Eryu Guan [this message]
2017-03-08 12:16 ` Dmitry Monakhov
-- strict thread matches above, loose matches on Subject: below --
2017-02-21 12:44 [PATCH 0/2] Add report generators support v2 Dmitry Monakhov
2017-02-21 12:44 ` [PATCH 2/2] report: Add xunit format report generator Dmitry Monakhov
2017-03-02 8:13 ` Eryu Guan
2017-01-31 17:43 [PATCH 0/2][RESEND] Add report generators support Dmitry Monakhov
2017-01-31 17:43 ` [PATCH 2/2] report: Add xunit format report generator Dmitry Monakhov
2017-02-16 10:08 ` Eryu Guan
2017-01-31 17:16 [PATCH 0/2] Add report generators support Dmitry Monakhov
2017-01-31 17:16 ` [PATCH 2/2] report: Add xunit format report generator Dmitry Monakhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170308030023.GW14226@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=amir73il@gmail.com \
--cc=dmonakhov@openvz.org \
--cc=fstests@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox