Working on an issue with connecting my HCI Connector example to the Testing Harness.
It will stop at breakpoints in my code (constructor) but will not test the full plugin.
Your configured plugin name in your plugin-test config file (see output for "Configured Plugin:") looks like it's:
BUT, your actual plugin name from the jar manifest looks like it's instead named:
Need to remove the extra "hornet" from your configured test plugin name.
Because you've configured a plugin for testing that does not actually exist in the plugin bundle, the test harness simply runs the basic manifest file validation logic against the jar without executing any of the connector execution tests on the plugin you meant to configure.
You are of course right and this worked as planned.
The odd thing is that I had noticed this before, had changed it and *thought* I pushed it upstream into GitHub. Looks like I was wrong and my assumption got me. Thanks for helping me out!
P.S. If you've modified the plugin since your config was created, you should always auto-generate an updated plugin config template for your jar file using:
./plugin-test -j <jarFilePath> -a <pathToConfig>
Then (after you edit the "pathToConfig" file to reflect the configuration you want to test), you can change the "-a" to "-c" and execute the tests using that config file. To debug, you can also add the "-d" switch. When a connector test runs, it should execute all the relevant connector API calls and hit your breakpoints.
Agreed, and that would have certainly bypassed this issue.
In this case however, I was trying to provide as few steps as possible for someone t download the plugin and make sure that it worked by providing the configuration. Seems it's better to leave these few steps in and talk about what they should be configured to, or perhaps set the defaults to the examples I wish to provide and generate the config file as you suggest.
Retrieving data ...