Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sHVha-008RBT-39 for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Jun 2024 21:40:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sHVhX-007p1n-Mo for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Jun 2024 21:40:16 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sHVhW-007p1S-Ko for pgsql-hackers@lists.postgresql.org; Wed, 12 Jun 2024 21:40:16 +0000 Received: from mail.clear-code.com ([153.126.206.245]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sHVhT-0011As-V9 for pgsql-hackers@postgresql.org; Wed, 12 Jun 2024 21:40:14 +0000 Received: from localhost (unknown [IPv6:2404:7a80:89c1:1200:6af9:2266:1443:f149]) by mail.clear-code.com (Postfix) with ESMTPSA id 302FCC0E04; Thu, 13 Jun 2024 06:40:04 +0900 (JST) DKIM-Filter: OpenDKIM Filter v2.11.0 mail.clear-code.com 302FCC0E04 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=clear-code.com; s=default; t=1718228404; bh=IO3gl0iWfwHqRs7MWrZnwLKQOCpqTdLAwpY0XyIHvtU=; h=Date:To:Cc:Subject:From:In-Reply-To:References:From; b=Yw9G+IVhg/LYqcCp9cidTgWnelf2oJd1Wj+0LbdwGpdmfxCrq2tKs8Y8C30avQZSr 401+HC/HMiacGs7AQWMWFzmDSGxb7OA7TUBF6Wf2mSbNK+Ni99gLaJ7focGBjCbnrH O45KOIzapplktzF0ot4xqgSpLo9J4TS/zKz4WUbQ= Date: Thu, 13 Jun 2024 06:40:01 +0900 (JST) Message-Id: <20240613.064001.1569077497664390798.kou@clear-code.com> To: jacob.champion@enterprisedb.com Cc: postgres@jeltef.nl, noah@leadboat.com, andres@anarazel.de, andrew@dunslane.net, pgsql-hackers@postgresql.org Subject: Re: RFC: adding pytest as a supported test framework From: Sutou Kouhei In-Reply-To: References: <20240611234829.9d@rfd.leadboat.com> X-Mailer: Mew version 6.8 on Emacs 29.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [1.40 / 999.00]; MID_CONTAINS_FROM(1.00)[]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:2518, ipnet:2404:7a80::/29, country:JP]; RCVD_COUNT_ZERO(0.00)[0]; RCPT_COUNT_FIVE(0.00)[6]; FROM_EQ_ENVFROM(0.00)[]; TO_DN_NONE(0.00)[]; SURBL_MULTI_FAIL(0.00)[enterprisedb.com:server fail,localhost:server fail] X-Rspamd-Server: mail.clear-code.com X-Rspamd-Action: no action X-Rspamd-Queue-Id: 302FCC0E04 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, (I don't have an opinion which language should be selected here.) In "Re: RFC: adding pytest as a supported test framework" on Wed, 12 Jun 2024 12:31:23 -0700, Jacob Champion wrote: > - I like Ruby as a language but have no experience using it for > testing. (RSpec did come up during the unconference session and > subsequent hallway conversations.) If we want to select Ruby, I can help. (I'm a Ruby committer and a maintainer of a testing framework bundled in Ruby.) I'm using Ruby for PGroonga's tests that can't be covered by pg_regress. For example, streaming replication related tests. PGroonga has a small utility for it: https://github.com/pgroonga/pgroonga/blob/main/test/helpers/sandbox.rb Here is a streaming replication test with it: https://github.com/pgroonga/pgroonga/blob/main/test/test-streaming-replication.rb I'm using test-unit as testing framework that is bundled in Ruby: https://github.com/test-unit/test-unit/ I don't recommend that we use RSpec as testing framework even if we select Ruby. RSpec may change API. (RSpec did it several times in the past.) If testing framework changes API, we need to rewrite our tests to adapt the change. I'll never change test-unit API because I don't want to rewrite existing tests. Thanks, -- kou