EqlActionIT runs multiple queries against an ES instance however:
-
Each test does not use a name but instead posts the actual query run making most, if not all tests, have invalid names thus no individual test can be tested individually.
A solution which would require modifying the toml would be adding names to each individual queries to indicate what they actually try to test.
-
Despite the @ClusterScope annotation, the suite creates one cluster per test (and all the setup that comes with it, such as setting up the index and destroying it). This might be caused by the @ParametersFactory annotation which trips the test runner.
Since the cause is unclear, so is the solution - if ParametersFactory is the cause then trying to figure out how to improve the underlying test runner or use a @ClassRule or something similar to keep the cluster around.
EqlActionITruns multiple queries against an ES instance however:Each test does not use a name but instead posts the actual query run making most, if not all tests, have invalid names thus no individual test can be tested individually.
A solution which would require modifying the toml would be adding names to each individual queries to indicate what they actually try to test.
Despite the
@ClusterScopeannotation, the suite creates one cluster per test (and all the setup that comes with it, such as setting up the index and destroying it). This might be caused by the@ParametersFactoryannotation which trips the test runner.Since the cause is unclear, so is the solution - if
ParametersFactoryis the cause then trying to figure out how to improve the underlying test runner or use a@ClassRuleor something similar to keep the cluster around.