Hi,
Bertrand Delacretaz schrieb:
I think there's only one thing missing for this to really work: we
should have a way of including automated tests in bundles, that can be
run in the actual Sling instance where the bundle is installed.
Having a list of testable bundles under /system/self-test, with a user
interface to run the tests, would make it much easier to test various
combinations of bundles. Shouldn't be too hard to implement if we
consider a test suite as an OSGi service.
While I fully agree with the need for tests and more tests and
integration tests etc, I do not have the best of all gut feelings
including tests into released binaries.
Tests belong to development/QA and the source and should not be
distributed with the actual binary. At the end of the day, this might
create more pain than relieve.
What we _must_ really care for is to ensure each bundle release is
backwards compatible - at least for the minor and micro release numbers.
We will have to take care of how to handle major release updates, which
allow for backwards-compatibility breaking.
Regards
Felix
