Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101738
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain mokrynskyi.com designates 46.4.12.50 as permitted sender)
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
References: <b81d6fa6-853b-26fc-d3a6-8a2eda58c349@mokrynskyi.com>
 <CAMbn9ZETaiG1R7RJVH1_3i99qz_TyHGAbXpBX23W2WyfR4N1-w@mail.gmail.com>
 <0b2d12f4-388c-a3bf-cbbf-417a0f98b386@mokrynskyi.com>
 <e8c4f7b6-6200-d4c4-1b44-bf2dca3cdc7e@gmail.com>
Organization: CleverStyle, Ecoisme
Message-ID: <4b80d345-d3dc-e7c7-9a73-f2352ddf0d8f@mokrynskyi.com>
Disposition-Notification-To: Nazar Mokrynskyi <nazar@mokrynskyi.com>
Date: Wed, 31 Jan 2018 12:50:38 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101
 Thunderbird/57.0
MIME-Version: 1.0
In-Reply-To: <e8c4f7b6-6200-d4c4-1b44-bf2dca3cdc7e@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Potential adoption of run-tests.php replacement
From: nazar@mokrynskyi.com (Nazar Mokrynskyi)

The idea is to make filenames more descriptive and sufficient for display=
ing in test results. This doesn't prevent or discourage anyone from inclu=
ding description in test file itself when more details need to be include=
d.

Moreover, all of the characters from mentioned title are allowed for use =
in file name (at least on Linux) and it would be much more useful to see =
them instead of 001.phpt or bug-1234.phpt.

Sincerely, Nazar Mokrynskyi
github.com/nazar-pc

31.01.18 00:26, Stanislav Malyshev =D0=BF=D0=B8=D1=88=D0=B5:
> Hi!
>
>> For instance, it is painful to work with tests in PHP source tree when=
 they are called 001.phpt, 002.phpt and so on - you need to open each fil=
e and read it to see what it intends to test. My tool uses file names ins=
tead, which makes browsing source tree with tests more productive and mak=
es --TEST-- section redundant (simply ignored).
> I think --TEST-- should absolutely be supported. Filename is not nearly
> enough to properly describe the content of the test. Something like
> "Test whether foo(bar($baz)) crashes if called more than twice (bug
> #1234)" is not going to be captured in a filename. Filenames and
> informative descriptions are not the same thing.
>
> I'll look more into what other requirements are needed (one suggestion
> would be try to keep option compatibility with the old tool if possible=
,
> so people could use their old habits) and write later, but I think
> supporting proper test descriptions would definitely be one of them.
>