[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZCkW8bFjy0GA0C34@google.com>
Date: Sat, 1 Apr 2023 22:47:29 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Javier Martinez Canillas <javierm@...hat.com>
Cc: linux-kernel@...r.kernel.org,
Enric Balletbo i Serra <eballetbo@...hat.com>,
Brendan Higgins <brendanhiggins@...gle.com>,
linux-kselftest@...r.kernel.org,
MaĆra Canal <mcanal@...lia.com>,
David Gow <davidgow@...gle.com>,
Daniel Latypov <dlatypov@...gle.com>,
kunit-dev@...glegroups.com, Maxime Ripard <maxime@...no.tech>,
linux-input@...r.kernel.org
Subject: Re: [PATCH v2] Input: Add KUnit tests for some of the input core
helper functions
On Thu, Mar 30, 2023 at 10:18:31AM +0200, Javier Martinez Canillas wrote:
> The input subsystem doesn't currently have any unit tests, let's add a
> CONFIG_INPUT_KUNIT_TEST option that builds a test suite to be executed
> with the KUnit test infrastructure.
>
> For now, only three tests were added for some of the input core helper
> functions that are trivial to test:
>
> * input_test_polling: set/get poll interval and set-up a poll handler.
>
> * input_test_timestamp: set/get input event timestamps.
>
> * input_test_match_device_id: match a device by bus, vendor, product,
> version and events capable of handling.
>
> But having the minimal KUnit support allows to add more tests and suites
> as follow-up changes. The tests can be run with the following command:
>
> $ ./tools/testing/kunit/kunit.py run --kunitconfig=drivers/input/tests/
>
> Signed-off-by: Javier Martinez Canillas <javierm@...hat.com>
> Tested-by: Enric Balletbo i Serra <eballetbo@...hat.com>
Applied, thank you.
--
Dmitry
Powered by blists - more mailing lists