Personally I don't have strong opinions either way: RefStack has the ability to run tests from both places, and are content to the let the projects/TC decide whether they want them to live somewhere centralized or not. However I thought it was worth mentioning that this is likely going to be a topic of a governance discussion soonish since you recommended taking an in-tree approach (in case foks feel strongly and want to weigh in). The POC I hacked up is actually in Tempest, but if folks feel strongly one way or another I'm happy to put it somewhere else.
That said, I think there are perhaps a few advantages to putting a new test like this in Tempest. For example, the most recent Board-approved DefCore Guideline covers Juno, Kilo, Liberty, and (now) Mitaka. Although we don't have a test for it, the version API itself has existed pretty much since forever in Neutron and should work just fine on all those releases. If we add the test to Tempest (which is branchless) users can get it quite easily. If we put it in-tree, we have to ask users to pull tests from master (or Newton once it arrives) even if the cloud they're working against is built on Kilo. So mechanically/logically, it's perhaps a bit easier on users.
Personally I don't have strong opinions either way: RefStack has the ability to run tests from both places, and are content to the let the projects/TC decide whether they want them to live somewhere centralized or not. However I thought it was worth mentioning that this is likely going to be a topic of a governance discussion soonish since you recommended taking an in-tree approach (in case foks feel strongly and want to weigh in). The POC I hacked up is actually in Tempest, but if folks feel strongly one way or another I'm happy to put it somewhere else.
That said, I think there are perhaps a few advantages to putting a new test like this in Tempest. For example, the most recent Board-approved DefCore Guideline covers Juno, Kilo, Liberty, and (now) Mitaka. Although we don't have a test for it, the version API itself has existed pretty much since forever in Neutron and should work just fine on all those releases. If we add the test to Tempest (which is branchless) users can get it quite easily. If we put it in-tree, we have to ask users to pull tests from master (or Newton once it arrives) even if the cloud they're working against is built on Kilo. So mechanically/ logically, it's perhaps a bit easier on users.