From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 1/6] xe_test_config.json: do some adjustments at the output hierarchy
Date: Tue, 14 Mar 2023 12:41:22 +0100 [thread overview]
Message-ID: <20230314114127.649447-2-mauro.chehab@linux.intel.com> (raw)
In-Reply-To: <20230314114127.649447-1-mauro.chehab@linux.intel.com>
From: Mauro Carvalho Chehab <mchehab@kernel.org>
Place "Mega feature" inside the same hierarchical level,
placing it on a higher level than sub-category, as this provides
a higher level of group for functionalities.
While here, better document the fields.
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
tests/xe/xe_test_config.json | 30 +++++++++++++++---------------
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/tests/xe/xe_test_config.json b/tests/xe/xe_test_config.json
index 6c474d6053f3..666fe6cd315c 100644
--- a/tests/xe/xe_test_config.json
+++ b/tests/xe/xe_test_config.json
@@ -4,27 +4,27 @@
"fields": {
"Category": {
"_properties_": {
- "description": "Contains the major group for the tested functionality"
+ "description": "Contains the major group for the tested functionality, being hardware, software or firmware"
},
- "Sub-category": {
+ "Mega feature": {
"_properties_": {
- "description": "Contains the minor group of the functionality"
- },
- "Functionality": {
- "_properties_": {
- "description": "Groups page table tests per functionality"
- }
+ "description": "Contains the mega feature for end to end use case, e. g. the 'sellable' feature."
},
- "Run type": {
+ "Sub-category": {
"_properties_": {
- "description": "Defines what category of testlist it belongs"
+ "description": "Contains the the technical feature/functionality"
+ },
+ "Functionality": {
+ "_properties_": {
+ "description": "Groups page table tests on buckets containg more detailed functionality"
+ }
+ },
+ "Run type": {
+ "_properties_": {
+ "description": "Defines what category of testlist it belongs"
+ }
}
}
- },
- "Mega feature": {
- "_properties_": {
- "description": "Contains the mega feature for E2E use case"
- }
}
},
"Test category": {
--
2.39.2
next prev parent reply other threads:[~2023-03-14 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 11:41 [igt-dev] [PATCH i-g-t 0/6] Do some improvements at igt_doc.py Mauro Carvalho Chehab
2023-03-14 11:41 ` Mauro Carvalho Chehab [this message]
2023-03-14 11:41 ` [igt-dev] [PATCH i-g-t 2/6] scripts/igt_doc.py: move show_subtests logic to the class Mauro Carvalho Chehab
2023-03-14 11:41 ` [igt-dev] [PATCH i-g-t 3/6] scripts/igt_doc.py: add support to generate testlists Mauro Carvalho Chehab
2023-03-14 11:41 ` [igt-dev] [PATCH i-g-t 4/6] scripts/igt_doc.py: prepare to place TestList class on a separate file Mauro Carvalho Chehab
2023-03-14 11:41 ` [igt-dev] [PATCH i-g-t 5/6] scripts/test_list.py: prepare to place " Mauro Carvalho Chehab
2023-03-14 11:41 ` [igt-dev] [PATCH i-g-t 6/6] scripts/igt_doc.py: re-introduce it by calling test_list.py Mauro Carvalho Chehab
2023-03-14 13:44 ` [igt-dev] ✓ Fi.CI.BAT: success for Do some improvements at igt_doc.py Patchwork
2023-03-15 17:40 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=20230314114127.649447-2-mauro.chehab@linux.intel.com \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@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