From: vlsi (@vlsi) <noreply+vlsi@github.com>
To: pgjdbc/pgjdbc <noreply+pgjdbc-pgjdbc@github.com>
Subject: Re: [pgjdbc/pgjdbc] PR #4251: OAuth implementation
Date: Thu, 25 Jun 2026 12:19:15 +0000
Message-ID: <gh-pgjdbc-pgjdbc-4251-c4799123989@github.com> (raw)
In-Reply-To: <gh-pgjdbc-pgjdbc-4251@github.com>
References: <gh-pgjdbc-pgjdbc-4251@github.com>
Just to clarify, we collect code coverage from a single ci job only which executes everything possible (see https://github.com/pgjdbc/pgjdbc/blob/be96a9b52636559139ce7a2f7d2b72f0efcf8d87/.github/workflows/mat...), so I would suggest:
1) `oauth_frontend=smoke` mode to execute only some tests (a single test class or two trying OAuth). This would be configured in coverage job.
2) `oauth_frontend=all` mode to execute all tests through oauth to surface issues like "batchtest fails if the driver connects via oauth". This would be helpful as a generic bug catcher.
In theory, it should result in proper PR diff coverage.
See https://app.codecov.io/gh/pgjdbc/pgjdbc/pull/4251