Re: RFC: adding pytest as a supported test framework

Hi,

(I don't have an opinion which language should be selected
here.)

In <CAOYmi+mA7-uNqpY-0jNZY=fE-QsbfeM1j5Mc-vu1Xm+=B8NOXA(at)mail(dot)gmail(dot)com>
"Re: RFC: adding pytest as a supported test framework" on Wed, 12 Jun 2024 12:31:23 -0700,
Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> 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