Weird behaviour when using `ConfigurationExtension` and standard config files about osgi-test HOT 10 OPEN

@stbischof any ideas?

from osgi-test.

There is a cleanup mechanism. Have to look how to disable/enable this via annotation

from osgi-test.

Just to add, the presence of the ConfigurationExtension also causes instability in configurations provided by File Install, with those configurations being spuriously updated for each test. This can then impact the reliability of subsequent tests.

from osgi-test.

One task of the ConfigurationExtension is to record the Configurations made in a test and reset them after each test.

https://github.com/osgi/osgi-test/blob/0e20db431c9857bd743c79fbc9f1ea4ce0211690/org.osgi.test.junit5.cm/src/main/java/org/osgi/test/junit5/cm/ConfigurationExtension.java#L318C15-L318C20

from osgi-test.

One task of the ConfigurationExtension is to record the Configurations made in a test and reset them after each test

Agreed - but shouldn't this only apply to configurations injected using @InjectConfiguration or created using @WithConfiguration? If they're installed by a different management agent then I think the test framework should leave them alone.

from osgi-test.

this would be a implementation that is much more what the user expect.

from osgi-test.

should be fixed by #777

from osgi-test.

Ilenia can retest in half a year :-(

from osgi-test.

The latest changes have definitely fixed this for me

from osgi-test.

Are we ok to close this issue now?

from osgi-test.