From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Pointers to Btrfs Testplan/Testcases
Date: Sat, 30 Jan 2016 13:30:54 +0000 (UTC) [thread overview]
Message-ID: <pan$5dcb5$1d9f47d2$78dd60b8$d9455195@cox.net> (raw)
In-Reply-To: 201601300847.u0U8kmnI021997@webminal.org
Lakshmipathi.G posted on Sat, 30 Jan 2016 09:46:48 +0100 as excerpted:
> I'm preparing/consolidating Btrfs testplan. Other than the testscripts
> available under btrfs-progs/tests repo (found
> https://fedoraproject.org/wiki/QA:Testcase_btrfs but its mainly for
> Installation) any pointers to wiki/testopia etc which will provide more
> details on it? I would like to avoid duplicate efforts. thanks.
As you suggest, the btrfs-progs tests are primarily to verify userspace
functionality after build; they aren't really designed for the more
general case. For that, btrfs, along with ext4 and of course xfs, now
use xfstests, which isn't just for xfs any more. In addition to the
general filesystem functionality tests, xfstests contains a full suite of
btrfs-specific tests for btrfs-specific functionality, and patches to
xfstests to catch new btrfs regressions should they occur again are not
only routinely seen on this list, but are often actively requested, if
not originally posted along with the patches fixing whatever btrfs bugs.
If you search the list archive on xfstests you'll see many examples.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-01-30 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 8:46 Pointers to Btrfs Testplan/Testcases Lakshmipathi.G
2016-01-30 13:30 ` Duncan [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-01 9:57 Lakshmipathi.G
2016-01-30 8:25 Lakshmipathi.G
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='pan$5dcb5$1d9f47d2$78dd60b8$d9455195@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).