DASH Shell discussions
 help / color / mirror / Atom feed
From: Michael Greenberg <michael@greenberg.science>
To: Brian Kuhl <brian.kuhl@windriver.com>,
	Andrej Shadura <andrew.shadura@collabora.co.uk>,
	dash <dash@vger.kernel.org>
Subject: Re: Testing dash on a new OS?
Date: Thu, 03 Feb 2022 10:15:05 -0500	[thread overview]
Message-ID: <m2r18kf0cm.fsf@greenberg.science> (raw)
In-Reply-To: <46266bf7-82ec-945e-7645-6d65b5393119@collabora.co.uk>

Bumping this old thread.

There are a few attempts at carefully testing POSIX shells:

  - POSIX <http://www.opengroup.org/testing/downloads.html>

  - Smoosh <https://github.com/mgree/smoosh/tree/master/tests>
    [disclaimer: I'm the author]

  - Oil
    <https://www.oilshell.org/release/latest/test/spec.wwz/survey/osh.html>

  - Yash <https://github.com/posix-shell-tests/posix-shell-tests>

  - Bash <https://git.savannah.gnu.org/cgit/bash.git/tree/tests>

None of these are a perfect fit for testing any of dash's particular
behaviors (e.g., dash treats non-lexical control differently from bash).

I would be _very_ interested in helping to build a test suite for POSIX
shells in general; I would be happy to also build a test suite for dash
in particular. Not only would such a test suite help identify
regressions in dash, it would also serve to document dash-specific
choices for unspecified and undefined behavior.

Cheers,
Michael

On 2021-11-02 at 01:47:53 PM, Andrej Shadura wrote:

> Hi,
>
> On 02/11/2021 01:45, Kuhl, Brian wrote:
>> Myself and an intern are working on porting dash to VxWorks.
>> https://www.windriver.com/products/vxworks
>> 
>> I've found harness for testing scripts, I haven't found anything for verifying dash itself?
>> How does Debian, or any other distro, (or for that matter a BSD),  regression test dash?
>
> Answering for Debian: we don’t really. There is only a smoke test 
> verifying dash exists and symlinks to it are all in place, but nothing 
> more than that at the moment.
>
> -- 
> Cheers,
>    Andrej

      reply	other threads:[~2022-02-03 15:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DM6PR11MB34686DFD31F7C9C07D3F8B1D998B9@DM6PR11MB3468.namprd11.prod.outlook.com>
2021-11-02  0:45 ` Testing dash on a new OS? Kuhl, Brian
2021-11-02 12:47   ` Andrej Shadura
2022-02-03 15:15     ` Michael Greenberg [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=m2r18kf0cm.fsf@greenberg.science \
    --to=michael@greenberg.science \
    --cc=andrew.shadura@collabora.co.uk \
    --cc=brian.kuhl@windriver.com \
    --cc=dash@vger.kernel.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