Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101736 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35792 invoked from network); 30 Jan 2018 22:26:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Jan 2018 22:26:39 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.52 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 74.125.83.52 mail-pg0-f52.google.com Received: from [74.125.83.52] ([74.125.83.52:40168] helo=mail-pg0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 14/84-24062-E11F07A5 for ; Tue, 30 Jan 2018 17:26:38 -0500 Received: by mail-pg0-f52.google.com with SMTP id g16so8397923pgn.7 for ; Tue, 30 Jan 2018 14:26:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=/vwICY/oOWyzCRJQitDnrNJVXMOr+jyxetQLsWvSZfk=; b=rIXlo8trCLNuW08ttlHS53vWDIFUjeKM8eQfs7IEXRlfMZr+x17rGhIusl0j0PNThe UW7ujCViaIhN1l2eZ4T/GgpX7M79Vqd3Od5o/DG1cYxWdiA9QJkaA7Jq1BmM1OkvTbrU noFJWEyaYWo7iJdUc0mOqsYqDSQojqxxhkik30Q5UR2FkK2DiBPIl9C5EZAfUgkuDlJd jjNwQ3FpVEmpkWBIRH1eNK+7c5jTxxVXM74NlJLqB0BjoUcx+lh3zk4pecjAfiEBl3jV sJdW0LOnO1CrQTdJTvJ9S1bIVgXxUA3IVJngJOV6DHVDDTVXubeSh9xzF3dg0BHjUvwi 5k7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=/vwICY/oOWyzCRJQitDnrNJVXMOr+jyxetQLsWvSZfk=; b=K9tRJ4P0I554OYrgHqJUXDcEHDMC36keWbI37CPDXYrIoRIs8b+MjeSrNGJ6tohEAS /SFQLeUVbrrgbwR2CvU1mS3fzRvBGDXnKzybddF3yFIENxD6iff2eadWLrA51yYGOxFV 1JK+UbG8+Rif1TkGxuH1bCwe/uYIBLSB6TULNg3ZGXk4UOFXaEhgEgw3GtQbJsoZWTRj HieVdMuydBi4E+knB9wZUMH/7NGgMGImDo+c4A9dbE8YCGjGLdIe8ksUI71AC04EfND+ FpIx472OVGhxCYsJZt987JMnoNhZJQAkRPfu8yr+VG+cr1uc+tLATLsAM2mrfAXxxvUi ixAw== X-Gm-Message-State: AKwxytcW/mNxjh5YRVgxuwMzKrVJXcvIE9DanQ/KiBOYKzcGWlxGeOFE amTFamYnARBtoqk0EuwHR9a22iI= X-Google-Smtp-Source: AH8x224/qkwqwQnL3LZ0gX+bhW4MFXv5SuOzHPG7nMVi1hh2wgkNVkTKrbVFGuZlqh65rCDkO/54iQ== X-Received: by 2002:a17:902:2702:: with SMTP id c2-v6mr24636399plb.342.1517351194651; Tue, 30 Jan 2018 14:26:34 -0800 (PST) Received: from Stas-Pro-2016.corp.wikimedia.org (tan4.corp.wikimedia.org. [198.73.209.4]) by smtp.gmail.com with ESMTPSA id d8sm6712670pfh.93.2018.01.30.14.26.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Jan 2018 14:26:33 -0800 (PST) To: Nazar Mokrynskyi Cc: PHP Internals References: <0b2d12f4-388c-a3bf-cbbf-417a0f98b386@mokrynskyi.com> Message-ID: Date: Tue, 30 Jan 2018 14:26:32 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:58.0) Gecko/20100101 Thunderbird/58.0 MIME-Version: 1.0 In-Reply-To: <0b2d12f4-388c-a3bf-cbbf-417a0f98b386@mokrynskyi.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Potential adoption of run-tests.php replacement From: smalyshev@gmail.com (Stanislav Malyshev) 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 file and read it to see what it intends to test. My tool uses file names instead, which makes browsing source tree with tests more productive and makes --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. -- Stas Malyshev smalyshev@gmail.com