From: Daniel Vetter <daniel@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 0/5] igt test naming conventions
Date: Mon, 4 Nov 2013 19:53:12 +0100 [thread overview]
Message-ID: <20131104185312.GP4167@phenom.ffwll.local> (raw)
In-Reply-To: <1383393876-2921-1-git-send-email-daniel.vetter@ffwll.ch>
On Sat, Nov 02, 2013 at 01:04:31PM +0100, Daniel Vetter wrote:
> Hi all,
>
> Spurred by the ongoing discussions about improving our tests I've started to
> document some of the naming patterns a bit. I've also added a few new ones and
> renamed a bunch of tests.
>
> The idea is that developers can use this patterns to construct add-hoc test
> groups with piglit's -t/-x options. I hope this here is a good start, but we
> certainly need to refine the patterns and test names over time.
>
> To ensure that we have sufficient coherency I propose the following rules:
> - If you add a large pile of new tests please document any new tests patterns in
> tests/NAMING-CONVENTIONS.
> - Any patches that are relevant for the test naming conventions must be posted
> to intel-gfx to keep everyone in the loop.
>
> Comments and ideas both on the patches and process highly welcome.
Ok I've pushed this after a bit of irc chatting. Please have a look at the
naming convention when writing new tests (or subtests). And if you see
some room to clarify things, patches (to intel-gfx) highly welcome.
-Daniel
>
> Cheeers, Daniel
>
> Daniel Vetter (5):
> tests: Start to document naming conventions
> tests: estbalish drv_ prefix
> tests: establish pm_ prefix
> tests: Use kms_ prefix a bit more
> tests: establish core_ prefix
>
> README | 3 +
> tests/.gitignore | 16 +-
> tests/Makefile.am | 26 +-
> tests/NAMING-CONVENTION | 63 ++++
> tests/ZZ_hangman | 70 ----
> tests/ZZ_missed_irq | 72 ----
> tests/core_getclient.c | 61 ++++
> tests/core_getstats.c | 50 +++
> tests/core_getversion.c | 49 +++
> tests/debugfs_pipe_crc.c | 262 --------------
> tests/debugfs_reader | 9 -
> tests/drv_debugfs_reader | 9 +
> tests/drv_hangman | 70 ++++
> tests/drv_missed_irq_hang | 72 ++++
> tests/drv_module_reload | 50 +++
> tests/drv_suspend.c | 171 +++++++++
> tests/gem_suspend.c | 171 ---------
> tests/getclient.c | 61 ----
> tests/getstats.c | 50 ---
> tests/getversion.c | 49 ---
> tests/kms_pipe_crc_basic.c | 262 ++++++++++++++
> tests/kms_sysfs_edid_timing | 25 ++
> tests/module_reload | 50 ---
> tests/pc8.c | 822 --------------------------------------------
> tests/pm_pc8.c | 822 ++++++++++++++++++++++++++++++++++++++++++++
> tests/pm_rc6_residency.c | 121 +++++++
> tests/pm_rps.c | 194 +++++++++++
> tests/sysfs_edid_timing | 25 --
> tests/sysfs_rc6_residency.c | 121 -------
> tests/sysfs_rps.c | 194 -----------
> 30 files changed, 2043 insertions(+), 1977 deletions(-)
> create mode 100644 tests/NAMING-CONVENTION
> delete mode 100755 tests/ZZ_hangman
> delete mode 100755 tests/ZZ_missed_irq
> create mode 100644 tests/core_getclient.c
> create mode 100644 tests/core_getstats.c
> create mode 100644 tests/core_getversion.c
> delete mode 100644 tests/debugfs_pipe_crc.c
> delete mode 100755 tests/debugfs_reader
> create mode 100755 tests/drv_debugfs_reader
> create mode 100755 tests/drv_hangman
> create mode 100755 tests/drv_missed_irq_hang
> create mode 100755 tests/drv_module_reload
> create mode 100644 tests/drv_suspend.c
> delete mode 100644 tests/gem_suspend.c
> delete mode 100644 tests/getclient.c
> delete mode 100644 tests/getstats.c
> delete mode 100644 tests/getversion.c
> create mode 100644 tests/kms_pipe_crc_basic.c
> create mode 100755 tests/kms_sysfs_edid_timing
> delete mode 100755 tests/module_reload
> delete mode 100644 tests/pc8.c
> create mode 100644 tests/pm_pc8.c
> create mode 100644 tests/pm_rc6_residency.c
> create mode 100644 tests/pm_rps.c
> delete mode 100755 tests/sysfs_edid_timing
> delete mode 100644 tests/sysfs_rc6_residency.c
> delete mode 100644 tests/sysfs_rps.c
>
> --
> 1.8.4.rc3
>
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2013-11-04 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 12:04 [PATCH 0/5] igt test naming conventions Daniel Vetter
2013-11-02 12:04 ` [PATCH 1/5] tests: Start to document " Daniel Vetter
2013-11-02 12:04 ` [PATCH 2/5] tests: estbalish drv_ prefix Daniel Vetter
2013-11-02 12:04 ` [PATCH 3/5] tests: establish pm_ prefix Daniel Vetter
2013-11-02 12:04 ` [PATCH 4/5] tests: Use kms_ prefix a bit more Daniel Vetter
2013-11-02 12:04 ` [PATCH 5/5] tests: establish core_ prefix Daniel Vetter
2013-11-04 18:53 ` Daniel Vetter [this message]
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=20131104185312.GP4167@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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