Fix MetricsTestBase

Begin/End metrics size depends on the timeout parameter value.

When a timeout is expected, a single begin/end metric should be listed, corresponding to the getConnection/close calls wrapping the tasks.

When a timeout isn't expected, the number of begin/end metric is the number of tasks plus one, corresponding to the getConnection/close calls.

Signed-off-by: Thomas Segismont <tsegismont@gmail.com>

Author: tsegismont

vertx-sql-client/src/test/java/io/vertx/tests/sqlclient/tck/MetricsTestBase.java

@@ -177,8 +177,8 @@ public void end(Object usageMetric) {
     ctx.assertEquals(0, queueSize.get());
     ctx.assertEquals(enqueueMetrics, dequeueMetrics);
     ctx.assertEquals(0, usageSize.get());
-    ctx.assertEquals(num, beginMetrics.size());
-    ctx.assertEquals(num, endMetrics.size());
+    ctx.assertEquals(timeout ? 1 : num + 1, beginMetrics.size());
+    ctx.assertEquals(timeout ? 1 : num + 1, endMetrics.size());
     ctx.assertEquals(beginMetrics, endMetrics);
     ctx.assertEquals("sql", poolType);
     ctx.assertEquals("the-pool", poolName);