public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH 0/7] Remove scsi testsuite + various testscripts
Date: Thu, 19 Oct 2023 09:22:08 +0200	[thread overview]
Message-ID: <20231019072208.GB33886@pevik> (raw)
In-Reply-To: <87r0lswdep.fsf@suse.de>

Hi Richie, all,

thanks for your review, merged.

> Hello,

> Petr Vorel <pvorel@suse.cz> writes:

> > Hi,

> > cleanup of 2 old scsi testsuites and some of legacy testscripts.
> > IMHO the testsuites are not worth of fixing.

> Very good. My only suggestion is to leave a tombstone in the
> documentation (or github issues) any time we delete something big and
> the thing it was supposed to test still should be tested.

I understand the need of missing coverage, preferably over github issue
(we document missing coverage over github issues already).

I wonder what should be noted in this case. These test scripts attempted to test:
* autofs (run other tests on autofs actually)
* BIO (we still have testcases/kernel/device-drivers/tbio/)
* sysfs (but we have at least some sysfs tests)
* SCSI (I suppose these will be better handled elsewhere - xfstests have
  scsi_debug file, mention scsi in some generic and xfs specific tests)
* device mapper tests (there is something ruby based:
https://github.com/jthornber/device-mapper-test-suite from Joe Thornber from Red
Hat)

> Something like "There was a testsuite called X, it appeared to do
> Y, but we had to remove it because of Z".

> It could be useful when answering questions about test feasability and
> for SEO.

I'm not sure if this 20 years old code deserves this description (but feel free
to write it if you think so). But identifying missing coverage is of course
important. Maybe we could have a special wiki page which would link missing
coverage issues [1], but also highlight the most important ones (big subsystem
missing) and also point out what we consider being tested elsewhere or what
would be hard to test with LTP thus should be tested elsewhere.

Kind regards,
Petr

[1] https://github.com/linux-test-project/ltp/labels/missing%20coverage

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2023-10-19  7:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16 18:44 [LTP] [RFC PATCH 0/7] Remove scsi testsuite + various testscripts Petr Vorel
2023-10-16 18:44 ` [LTP] [RFC PATCH 1/7] doc: Remove ltp-run-files.txt Petr Vorel
2023-10-16 18:44 ` [LTP] [RFC PATCH 2/7] fs: Remove scsi/ltpfs testsuite Petr Vorel
2023-10-16 18:44 ` [LTP] [RFC PATCH 3/7] fs: Remove scsi/ltpscsi testsuite Petr Vorel
2023-10-16 18:44 ` [LTP] [RFC PATCH 4/7] testscripts: Remove ltpdmmapper.sh Petr Vorel
2023-10-16 18:44 ` [LTP] [RFC PATCH 5/7] testscripts: Remove ltp-scsi_debug.sh Petr Vorel
2023-10-16 18:44 ` [LTP] [RFC PATCH 6/7] testscripts: Remove sysfs.sh Petr Vorel
2023-10-16 18:44 ` [LTP] [RFC PATCH 7/7] testcases: Remove autofs{1,4}.sh scripts Petr Vorel
2023-10-17 10:41 ` [LTP] [RFC PATCH 0/7] Remove scsi testsuite + various testscripts Marius Kittler
2023-10-17 15:07 ` Cyril Hrubis
2023-10-18  7:11 ` Li Wang
2023-10-18  8:04 ` Richard Palethorpe
2023-10-19  7:22   ` Petr Vorel [this message]
2023-10-19  7:34     ` Richard Palethorpe

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=20231019072208.GB33886@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=rpalethorpe@suse.de \
    /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