On Wed, Jun 21, 2017 at 05:07:12PM -0700, Adam Williamson wrote:
'dummy' python3-kickstart package, with a NEVR known to be lower than any 'real' version of the package, so we know for sure that an update will be available from the official repositories, and then we go ahead and run an update in the usual fashion. Would there be any similar kind of possibility for testing ostree updates? The goals of openQA testing are to test as 'realistically' as possible, so we only test unmodified images, and want to have the test behave as similarly as possible to how the 'real' operation would behave on an end user's system.
You should be able to go back and forth between various ostree commits, right? Possibly in addition to a "do full install, test" thing, there could just be a "update from previous to new, test" image. Or, am I misunderstanding?