On 2/14/19 4:56 PM, Brendan Higgins wrote:
On Thu, Feb 14, 2019 at 3:57 PM Frank Rowand
> On 12/5/18 3:54 PM, Brendan Higgins wrote:
>> On Tue, Dec 4, 2018 at 2:58 AM Frank Rowand <frowand.list(a)gmail.com>
>>> Hi Brendan,
>>> On 11/28/18 11:36 AM, Brendan Higgins wrote:
>>>> Split out a couple of test cases that these features in base.c from the
>>>> unittest.c monolith. The intention is that we will eventually split out
>>>> all test cases and group them together based on what portion of device
>>>> tree they test.
>>> Why does splitting this file apart improve the implementation?
>> This is in preparation for patch 19/19 and other hypothetical future
>> patches where test cases are split up and grouped together by what
>> portion of DT they test (for example the parsing tests and the
>> platform/device tests would probably go separate files as well). This
>> patch by itself does not do anything useful, but I figured it made
>> patch 19/19 (and, if you like what I am doing, subsequent patches)
>> easier to review.
> I do not see any value in splitting the devicetree tests into
> multiple files.
> Please help me understand what the benefits of such a split are.
Note that my following comments are specific to the current devicetree
unittests, and may not apply to the general case of unit tests in other
Sorry, I thought it made sense in context of what I am doing in the
following patch. All I am trying to do is to provide an effective way
of grouping test cases. To be clear, the idea, assuming you agree, is
Looking at _just_ the first few fragments of the following patch, the
change is to break down a moderate size function of related tests,
of_unittest_find_node_by_name(), into a lot of extremely small functions.
Then to find the execution order of the many small functions requires
finding the array of_test_find_node_by_name_cases. Then I have to
chase off into the kunit test runner core, where I find that the set
of tests in of_test_find_node_by_name_cases is processed by a
late_initcall(). So now the order of the various test groupings,
declared via module_test(), are subject to the fragile orderings
There are ordering dependencies within the devicetree unittests.
I do not like breaking the test cases down into such small atoms.
I do not see any value __for devicetree unittests__ of having
such small atoms.
It makes it harder for me to read the source of the tests and
understand the order they will execute. It also makes it harder
for me to read through the actual tests (in this example the
tests that are currently grouped in of_unittest_find_node_by_name())
because of all the extra function headers injected into the
existing single function to break it apart into many smaller
Breaking the tests into separate chunks, each chunk invoked
independently as the result of module_test() of each chunk,
loses the summary result for the devicetree unittests of
how many tests are run and how many passed. This is the
only statistic that I need to determine whether the
unittests have detected a new fault caused by a specific
patch or commit. I don't need to look at any individual
test result unless the overall result reports a failure.
that we would follow up with several other patches like this one and
the subsequent patch, one which would pull out a couple test
functions, as I have done here, and another that splits those
functions up into a bunch of proper test cases.
I thought that having that many unrelated test cases in a single file
would just be a pain to sort through deal with, review, whatever.
Having all the test cases in a single file makes it easier for me to
read, understand, modify, and maintain the tests.
This is not something I feel particularly strongly about, it is just
pretty atypical from my experience to have so many unrelated test
cases in a single file.
Maybe you would prefer that I break up the test cases first, and then
we split up the file as appropriate?
I prefer that the test cases not be broken up arbitrarily. There _may_
be cases where the devicetree unittests are currently not well grouped
and may benefit from change, but if so that should be handled independently
of any transformation into a KUnit framework.
I just assumed that we would agree it would be way too much stuff
a single file, so I went ahead and broke it up first, because I
thought it would make it easier to review in that order rather than
the other way around.