-
Notifications
You must be signed in to change notification settings - Fork 18
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ci: use better default options for NeonBee in tests
During investigation of build problems the issue was located that in our tests we have had multiple different ways we used to initialize NeonBee sometimes with and sometimes without a associated NeonBee instance: - NeonBee.create - registerNeonBeeMock - NeonBeeExtension/NeonBeeInstanceConfiguration Each time NeonBee was initialized we used a different set of options. Especially for tests particular set of NeonBeeOptions is important, e.g. not to scan the class path or not starting the WatchVerticles. Because of the different options how to start Vert.x these options have often been neglected. This commit uses the same set of default options for all the different ways a NeonBee instance is created. Now when creating a request (with the NeonBeeTestBase.createRequest method), in case the server port is specified in the options, it is preferred over the server port in the server verticle configuration file.
- Loading branch information
Showing
14 changed files
with
347 additions
and
147 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.