How have folks approached writing a <test suite> t...
# general
c
How have folks approached writing a test suite to be used while upgrading? These are the questions I'm most interested in right now: • Do you write tests for all of your queries or a subset? What does it take to gain confidence in the upgrade? • How do you deal with shared state between tests as your test suite grows (they all read from the same underlying table with data added for each test)? How do you reason about tests in a large suite given shared state?
On closer reading, I think the answer to my first question is at the bottom of the docs.
As a good practice, we suggest that you build your own test suite that has the tables, schemas, queries, and system configurations used in your installation of Pinot, so that you can verify compatibility for the features/configurations that your cluster uses.
Sounds like the suggested way to gain confidence is to get complete test coverage.