public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivan Orlov <ivan.orlov0322@gmail.com>
To: David Gow <davidgow@google.com>
Cc: brendan.higgins@linux.dev, rmoar@google.com,
	linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] kunit: Merge assertion test into kunit-test.c
Date: Tue, 11 Jun 2024 14:10:04 +0100	[thread overview]
Message-ID: <37fcb821-e49f-4f9e-a1d2-1d18d40ea61c@gmail.com> (raw)
In-Reply-To: <CABVgOSkc+t0J2tbgRHnsao9mhhDDKcjp+62R+F_fUQv7aBvTbA@mail.gmail.com>

On 6/8/24 10:20, David Gow wrote:
> On Tue, 4 Jun 2024 at 20:32, Ivan Orlov <ivan.orlov0322@gmail.com> wrote:
>>
>> Since assert_test covers the part of the KUnit core (the assertion
>> formatting functions), I believe it would be better to have it merged
>> into kunit-test (as it is done for other tests for the KUnit core).
>>
>> Signed-off-by: Ivan Orlov <ivan.orlov0322@gmail.com>
>> ---
> 
> Personally, I don't mind if the assert tests are in a separate file,
> but do think it's worth having them in the same module.
> 
> Do you think it'd be better to keep them as separate source files (but
> put them in the same module via the Makefile), or is having a single
> source file cleaner?
> 
> Either way, I think this should be merged with the previous patch (see
> my comments there.)
> 

Hi David,

Thank you for the review and sorry for the late reply.

I believe having the assert test in the same file as other kunit core 
tests would be more consistent with the existing test structure 
(otherwise, the tests for other parts of the kunit core should be 
extracted to separate files as well).

What do you think is more appropriate?

-- 
Kind regards,
Ivan Orlov


      reply	other threads:[~2024-06-11 13:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 12:31 [PATCH 0/5] Reorganize string-stream and assert tests Ivan Orlov
2024-06-04 12:32 ` [PATCH 1/5] kunit: string-stream: export non-static functions Ivan Orlov
2024-06-08  9:20   ` David Gow
2024-06-09 19:01     ` Ivan Orlov
2024-06-04 12:32 ` [PATCH 2/5] kunit: kunit-test: Remove stub for log tests Ivan Orlov
2024-06-08  9:20   ` David Gow
2024-06-04 12:32 ` [PATCH 3/5] kunit: string-stream-test: Make it a separate module Ivan Orlov
2024-06-08  9:20   ` David Gow
2024-06-04 12:32 ` [PATCH 4/5] kunit: assert: export non-static functions Ivan Orlov
2024-06-08  9:20   ` David Gow
2024-06-09 19:05     ` Ivan Orlov
2024-06-04 12:32 ` [PATCH 5/5] kunit: Merge assertion test into kunit-test.c Ivan Orlov
2024-06-08  9:20   ` David Gow
2024-06-11 13:10     ` Ivan Orlov [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=37fcb821-e49f-4f9e-a1d2-1d18d40ea61c@gmail.com \
    --to=ivan.orlov0322@gmail.com \
    --cc=brendan.higgins@linux.dev \
    --cc=davidgow@google.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=rmoar@google.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