From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/3] tests: rename feature_discovery to kms_feature_discovery
Date: Fri, 8 Sep 2023 11:21:09 +0530 [thread overview]
Message-ID: <70f8cb6b-b3cd-defa-3466-b2c7101142b7@intel.com> (raw)
In-Reply-To: <20230907173310.nb5ttfmfqsnqdwat@kamilkon-desk.igk.intel.com>
On 07-Sep-23 11:03 PM, Kamil Konieczny wrote:
> Hi Swati,
>
> On 2023-09-07 at 20:02:12 +0530, Swati Sharma wrote:
>> Since feature discovery test is only having kms tests,
>> rename to kms_feature_discovery. Also, add documentation
>> for the subtests.
>>
>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
>> ---
>> ...re_discovery.c => kms_feature_discovery.c} | 53 ++++++++++++++++++-
>> tests/meson.build | 2 +-
>> 2 files changed, 53 insertions(+), 2 deletions(-)
>> rename tests/{feature_discovery.c => kms_feature_discovery.c} (68%)
>>
>> diff --git a/tests/feature_discovery.c b/tests/kms_feature_discovery.c
>> similarity index 68%
>> rename from tests/feature_discovery.c
>> rename to tests/kms_feature_discovery.c
>> index d1f4b1633..49958fd88 100644
>> --- a/tests/feature_discovery.c
>> +++ b/tests/kms_feature_discovery.c
>> @@ -22,6 +22,58 @@
>> *
>> */
>>
>> +/**
>> + * TEST: kms feature discovery
>> + * Category: Display
>> + * Description: A metatest that checks for \"features\" presence.
>> + * The subtests here should only skip or pass,
>> + * anything else means we have a serious problem.
>> + *
>> + * SUBTEST: display
>> + * Description: Make sure that we have display support with
>> + * some outputs connected.
>> + * Driver requirement: i915, xe
>> + * Functionality: feature_discovery
>> + * Mega feature: General Display Features
>> + * Run type: FULL
>> + * Test category: functionality test
>> + *
>> + * SUBTEST: display-%dx
>> + * Description: Make sure that we have display support with %arg[1]
>> + * outputs connected.
>> + * Driver requirement: i915, xe
>> + * Functionality: feature_discovery
>> + * Mega feature: General Display Features
>> + * Run type: FULL
>> + * Test category: functionality test
>> + *
>> + * SUBTEST: chamelium
>> + * Description: Make sure that Chamelium is configured and reachable.
>> + * Driver requirement: i915, xe
>> + * Functionality: feature_discovery, chamelium
>> + * Mega feature: General Display Features
>> + * Run type: FULL
>> + * Test category: functionality test
>> + *
>> + * SUBTEST: psr1
>> + * Description: Make sure that we have eDP panel with PSR1 support.
>> + * Driver requirement: i915, xe
>> + * Functionality: feature_discovery, psr1, eDP
>> + * Mega feature: General Display Features
>> + * Run type: FULL
>> + * Test category: functionality test
>> + *
>> + * SUBTEST: psr2
>> + * Description: Make sure that we have eDP panel with PSR2 support.
>> + * Driver requirement: i915, xe
> ----- ^
>
>> + * Functionality: feature_discovery, psr2, eDP
>> + * Mega feature: General Display Features
> ----- ^
>
>> + * Run type: FULL
> ----- ^
>
>> + * Test category: functionality test
> ----- ^
> All these fields are the same for all SUBTEST:, imho we should
> move them into TEST: and save some space. With that:
>
> Acked-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>
> Regards,
> Kamil
Hi Kamil,
This might be valid for today but in future if we need to extend test
having different fields, this might not to be true.
For other kms tests too, we have done testplan documentation at
subtest level only.
>
>> + *
>> + * arg[1].values: 2, 3, 4
>> + */
>> +
>> #include "igt.h"
>> #ifdef HAVE_CHAMELIUM
>> #include "igt_chamelium.h"
>> @@ -46,7 +98,6 @@ igt_main {
>> }
>>
>> igt_subtest_group {
>> -
>> igt_fixture {
>> igt_display_require(&display, fd);
>> }
>> diff --git a/tests/meson.build b/tests/meson.build
>> index aa8e3434c..eb643d4dd 100644
>> --- a/tests/meson.build
>> +++ b/tests/meson.build
>> @@ -14,7 +14,6 @@ test_progs = [
>> 'drm_mm',
>> 'drm_read',
>> 'fbdev',
>> - 'feature_discovery',
>> 'kms_3d',
>> 'kms_addfb_basic',
>> 'kms_async_flips',
>> @@ -31,6 +30,7 @@ test_progs = [
>> 'kms_dither',
>> 'kms_display_modes',
>> 'kms_dp_aux_dev',
>> + 'kms_feature_discovery',
>> 'kms_flip',
>> 'kms_flip_event_leak',
>> 'kms_force_connector_basic',
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2023-09-08 5:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 14:32 [igt-dev] [PATCH i-g-t 0/3] enable feature-discovery tests Swati Sharma
2023-09-07 14:32 ` [igt-dev] [PATCH i-g-t 1/3] tests: rename feature_discovery to kms_feature_discovery Swati Sharma
2023-09-07 16:38 ` Modem, Bhanuprakash
2023-09-07 17:33 ` Kamil Konieczny
2023-09-08 5:51 ` Sharma, Swati2 [this message]
2023-09-07 14:32 ` [igt-dev] [PATCH i-g-t 2/3] tests/intel-ci: remove feature_discovery from blocklist Swati Sharma
2023-09-07 17:33 ` Kamil Konieczny
2023-09-07 14:32 ` [igt-dev] [PATCH i-g-t 3/3] tests/kms_feature_discovery: detect mst configuration Swati Sharma
2023-09-07 16:47 ` Modem, Bhanuprakash
2023-09-07 16:09 ` [igt-dev] ✓ CI.xeBAT: success for enable feature-discovery tests Patchwork
2023-09-07 16:13 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-09-07 18:21 ` [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=70f8cb6b-b3cd-defa-3466-b2c7101142b7@intel.com \
--to=swati2.sharma@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
/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