Is there some best practice to automatically test setups?

[ingomohr]

Dear all,

we maintain a number of setups for custom IDE configurations, project import tasks and preference tasks in our own Oomph Git repository.
We are testing our changes in those *.setup files manually, but this is both expensive and error-prone.

Is there a way of running automated tests to have proof that the setups will work as expected in the installer?

Thank you very much in advance for your thoughts!

Kind regards
Ingo

[merks]

That's a very good question for which I have a very poor answer. We don't have such tests either, but there would certainly be value in such things. 😱

One general problem of course is that various things are prompted so one needs to provide such values. One place where we do sort of run such tests is here where we are generating setups to test marketplace listings:

org.eclipse.oomph.setup.internal.installer.MarketplaceCatalogGenerator.test()

I've not looked in detail at this project:

https://github.com/a-langer/eclipse-oomph-console

But I assume that in principle, this could be used to drive tests. I would be very much interest in your experience with that if you try it.

[ingomohr]

Thank you @merks for your quick response and the links! I'll have a look and hope I can give you an update myself soon. :)

[szarnekow]

@ingomohr Did you figure a mechanism to automatically test setups?

[ingomohr]

Hi @szarnekow - no, sorry. I had other problems to tackle in the meantime. I'm still interested in this topic, though. Just didn't find the time.