From: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Pavel Shilovsky
<piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Shirish Pargaonkar
<shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
luk-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org
Subject: Regression tests for CIFS client
Date: Wed, 08 Aug 2012 17:31:09 +0530 [thread overview]
Message-ID: <50225505.3080303@suse.com> (raw)
Hi everyone,
The CIFS client never had proper regression tests and we try to tweak
the connectathon tests a little bit and run to avoid regressions
creeping in. I think a testsuite that checks for regressions would be
useful.
I spent sometime hacking up a set of tests. These tests use Python and
PyUnit framework which I think might help quickly adding newer tests.
Tests are written based on the past bug reports and experiences.
The primary intent of the tests is to provide some basic infrastructure
upon which tests can be added easily in the future and these tests are
by no means comprehensive. I have tried to avoid duplicating tests
already done by Connectathon and other tests but there could still be a
few duplicates in there. The tests are only lightly tested.
Currently cifstests is hosted here:
https://github.com/sureshjayaram/cifstests
Feel free to try out and let me know your feedback or any comments and
suggestions.
Here's are the failures seen with 3.1 based kernel. I think the open()
with O_DIRECT is expected to fail since cifs doesn't support it (I'd be
interesting in knowing exact details). But, I've not dig into the xattr
tests, not sure why setattr is failing (even if CIFS_XATTR is set, fs
mounted with user_xattr).
Test Output
============
======================================================================
ERROR: test_directIO (__main__.OpenTests)
open a file with O_DIRECT
----------------------------------------------------------------------
Traceback (most recent call last):
File "./testcifs.py", line 144, in test_directIO
raise e
OSError: [Errno 22] Invalid argument: 'testfile'
======================================================================
ERROR: test_dir_attr (__main__.XattrTests)
set attrs, get attrs and remove attrs for a dir
----------------------------------------------------------------------
Traceback (most recent call last):
File "./testcifs.py", line 364, in test_dir_attr
raise e
IOError: [Errno 95] Operation not supported: 'test'
======================================================================
ERROR: test_file_attr (__main__.XattrTests)
set attrs, get attrs and remove attrs for a file
----------------------------------------------------------------------
Traceback (most recent call last):
File "./testcifs.py", line 343, in test_file_attr
raise e
IOError: [Errno 95] Operation not supported: 'testfile'
----------------------------------------------------------------------
Ran 22 tests in 0.072s
FAILED (errors=3)
What do you think? Is it be a good idea?
I know I have barely scratched the surface, but any suggestion on having
a working regression test is welcome. And of course, regression tests
are supposed to evolve over time. Would this be a convenient way to add
more tests?
Thanks
Suresh
next reply other threads:[~2012-08-08 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 12:01 Suresh Jayaraman [this message]
[not found] ` <50225505.3080303-IBi9RG/b67k@public.gmane.org>
2012-08-08 12:41 ` Regression tests for CIFS client Jeff Layton
[not found] ` <20120808084149.26325074-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2012-08-08 13:50 ` Steve French
[not found] ` <CAH2r5mt_ss8YGYLRjQ5dKiRntWCribtScFOtz3hTno6TJQXQqA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-09 14:45 ` Suresh Jayaraman
2012-08-09 14:37 ` Suresh Jayaraman
[not found] ` <5023CB44.8000802-IBi9RG/b67k@public.gmane.org>
2012-08-09 15:03 ` Jeff Layton
[not found] ` <20120809110351.22847557-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-08-10 5:27 ` Suresh Jayaraman
[not found] ` <50249BC7.2000205-IBi9RG/b67k@public.gmane.org>
2012-08-10 10:41 ` Jeff Layton
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=50225505.3080303@suse.com \
--to=sjayaraman-ibi9rg/b67k@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=luk-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org \
--cc=piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.