CharliePoole
commented
2 years ago Re-thinking this, I changed it to (plural) extensions. I think we need a dummy extension in the build for each extension point we intend to support. They can be very simple... they only need to indicate that they are installed and that there methods have been called in some way. They could start as simple fakes and enhanced to be true mocks only if necessary.
Given our current decisions about support, there would be six of them, but possibly bundled in a single assembly for simplicity. They should install somewhere in the output directory where our tests could find and install them. They would only be used for unit tests... package tests would continue to use actual extensions where needed.
Followup on a separate discussion... This would be used to test the loading of extensions. It will be built for each runtime we support and will enable testing of the engine.
To the extent possible, the extension should be instrumented to report when it is loaded, initialized or unloaded and which runtime version is actually chosen.