From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 1C1B01F5AE; Mon, 22 Jun 2020 17:51:29 +0000 (UTC) Date: Mon, 22 Jun 2020 17:51:28 +0000 From: Eric Wong To: meta@public-inbox.org Subject: TAP output for user-facing tools? Message-ID: <20200622175128.GA6811@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Hey all, so I've been wondering about how to express debug/tracing output to user-facing command-line tools. Our test suite already uses TAP. So does git.git, Perl itself and the majority of Perl projects I've encountered. But I haven't seen it used for user-facing CLI tools... It seems better than inventing random new formats *shrug* TAP = Test Anything Protocol: https://testanything.org/