[FEATURE REQUEST] Reusable integration tests

[dimas-b]

Is your feature request related to a problem? Please describe.

Currently integration tests use TestEnvironmentExtension that is intended to provide multiple execution environments, but at the same time depend on DropwizardExtensionsSupport that automatically starts a local DW server.

Describe the solution you'd like

• Sharable suite of tests that can be executed against different Polaris servers.
• Polaris Server lifecycle delegated to the test environment.
• CI continues to use Dropwizard for integration tests, but in a "backbox" manner (tweaking only via standard config options).

Describe alternatives you've considered

No response

Additional context

No response

[dimas-b]

I'm working on PR for this issue ⌛

[collado-mike]

@andrew4699 has done some work here - it would be good if he can also help define requirements

[dimas-b]

I put my notes above. We also have a Zulip thread on this.

[andrew4699]

This sounds great. Today you can jump through a series of hoops and run tests against any Polaris server but it's wasteful (due to always spinning up a DW instance) and not intuitive (only 1 test class supported/distinction between local DW and remote is unclear).

I'm happy to help with implementation once things are less busy. The implementation may also look a bit different in Quarkus vs DW.

[dimas-b]

@andrew4699 : Please review #590

[andrew4699]

Typing from my phone… I’m out through the 6th but will look when I get a chance.

[dimas-b]

#590 looks sufficient for now from my POV. Closing this issue.