Here are my takeaways from the previous discussions:
* there *is* interest in testing
* we shouldn't take it too far
* there are already tests being written under `src/test/modules`, but without a consistent way of describing expectations and displaying results
* no tool was chosen
If we were to use this tool, would the community want to vendor the framework in the Postgres repository, or keep it in a separate repository that produces a versioned shared library?
> On Fri, Jun 28, 2019 at 11:38 AM Adam Berlin <aberlin@pivotal.io> wrote: > > During the unconference at PGCon in Ottawa, I asked about writing C-based > tests for Postgres. There was interest in trying a tool and also some > hesitation to depend on a third-party library. So, I wrote a tool that I'd > like to contribute to Postgres. I’ve been calling it cexpect [1].
Cool, thanks!
> Rather than post a patch, I'd rather start a conversation first. I'm guessing > there are some improvements that we'd want to make (for example: the > Makefile) before commiting a patch. Let's iterate on improvements before > creating a formal patch.
Just to mention, there were similar discussions already in the past ([1], [2]), with some concerns being raised, but looks like without any visible results.
