Background:
Currently, mocks have to be configured programmatically with @BeforeAll methods. For simplicity's sake, most mocks could have some form of basic config applied automatically from Knot.x config files, and only edge cases would have to get configured in dedicated methods.
What is already present:
KnotxMockConfig data object for storing mocks config
KnotxFileSource override for WireMock
Steps needed:
[x] Read Knot.x config (see #16, some of the work will be done there)
[x] Load config from test.wiremock.<mock_identifier> config namespace
[x] Extend existing and implement new functionality
[x] Configuring WiremockServer through given method
[x] Provide option for basic server configuring (request path to resource path mapping, mimetype, port)
[x] Start up mock servers
Recommended to test this feature on knotx-stack or knotx-data-bridge modules, ideally on both.
Background:
Currently, mocks have to be configured programmatically with
@BeforeAllmethods. For simplicity's sake, most mocks could have some form of basic config applied automatically from Knot.x config files, and only edge cases would have to get configured in dedicated methods.What is already present:
KnotxMockConfigdata object for storing mocks configKnotxFileSourceoverride for WireMockSteps needed:
test.wiremock.<mock_identifier>config namespaceRecommended to test this feature on knotx-stack or knotx-data-bridge modules, ideally on both.