Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Shuah Khan <skhan@linuxfoundation.org>, Shuah Khan <shuah@kernel.org>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
	Aleksa Sarai <cyphar@cyphar.com>,
	kernel@collabora.com, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] selftests: openat2: don't print total number of tests and then skip
Date: Fri, 2 Aug 2024 10:40:01 +0500	[thread overview]
Message-ID: <c66ab6ff-c9e1-4935-95a5-67e8b83962a3@collabora.com> (raw)
In-Reply-To: <2e1509f5-2a10-4876-8619-6a6b9c29d269@linuxfoundation.org>

On 8/1/24 10:27 PM, Shuah Khan wrote:
> On 8/1/24 10:27, Shuah Khan wrote:
>> On 8/1/24 02:42, Muhammad Usama Anjum wrote:
>>> On 7/31/24 9:57 PM, Shuah Khan wrote:
>>>> On 7/31/24 07:39, Muhammad Usama Anjum wrote:
>>>>> Don't print that 88 sub-tests are going to be executed, but then skip.
>>>>> This is against TAP compliance. Instead check pre-requisites first
>>>>> before printing total number of tests.
>>>>
>>>> Does TAP clearly mention this?
>>> Yes from https://testanything.org/tap-version-13-specification.html
>>>
>>> Skipping everything
>>> This listing shows that the entire listing is a skip. No tests were run.
>>>
>>> TAP version 13
>>> 1..0 # skip because English-to-French translator isn't installed
>>
> 
> One more thing on TAP compliance - we don't strive to be TAP compliant
> as it doesn't meet our special needs.
> 
> It is important to keep the how many tests could be run to improve testing
> coverage.
> 
> Refer to: https://www.kernel.org/doc/html/latest/dev-tools/ktap.html
> 
> "The Linux Kernel largely uses TAP output for test results. However, Kernel
> testing frameworks have special needs for test results which don’t align with
> the original TAP specification. Thus, a “Kernel TAP” (KTAP) format is
> specified
> to extend and alter TAP to support these use-cases. This specification
> describes
> the generally accepted format of KTAP as it is currently used in the kernel."
> 
> I appreciate the effort you are putting into improving the reports. I request
> that you refer to the above document and also keep in mind what would help us
> improve our testing over focusing just on reports and compliance.
That makes sense. I'll work on improving the testing going forward.

> 
> thanks,
> -- Shuah
> 

-- 
BR,
Muhammad Usama Anjum

  reply	other threads:[~2024-08-02  5:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 13:39 [PATCH v2] selftests: openat2: don't print total number of tests and then skip Muhammad Usama Anjum
2024-07-31 14:58 ` Aleksa Sarai
2024-07-31 16:57 ` Shuah Khan
2024-08-01  8:42   ` Muhammad Usama Anjum
2024-08-01 16:27     ` Shuah Khan
2024-08-01 17:27       ` Shuah Khan
2024-08-02  5:40         ` Muhammad Usama Anjum [this message]
2024-08-02  5:38       ` Muhammad Usama Anjum
2024-08-02 23:10         ` Shuah Khan

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=c66ab6ff-c9e1-4935-95a5-67e8b83962a3@collabora.com \
    --to=usama.anjum@collabora.com \
    --cc=cyphar@cyphar.com \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.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