ignoring testFetch as it is long time to execute

ignoring the testFetch method as it is taking 130 sec to execute, as
reported by Patrick in the issue APPC-1111.

Issue-ID: APPC-1111
Change-Id: I7bef0719a04b5d3dd9d52a1c2608f16f16d76c5d
Signed-off-by: Sandeep J <sandeejh@in.ibm.com>

diff --git a/appc-adapters/appc-dmaap-adapter/appc-dmaap-adapter-bundle/src/test/java/org/onap/appc/adapter/messaging/dmaap/impl/TestDmaapConsumerImpl.java b/appc-adapters/appc-dmaap-adapter/appc-dmaap-adapter-bundle/src/test/java/org/onap/appc/adapter/messaging/dmaap/impl/TestDmaapConsumerImpl.java
index dd76ef6..c7f3837 100644 (file)
--- a/appc-adapters/appc-dmaap-adapter/appc-dmaap-adapter-bundle/src/test/java/org/onap/appc/adapter/messaging/dmaap/impl/TestDmaapConsumerImpl.java
+++ b/appc-adapters/appc-dmaap-adapter/appc-dmaap-adapter-bundle/src/test/java/org/onap/appc/adapter/messaging/dmaap/impl/TestDmaapConsumerImpl.java
@@ -105,7 +105,7 @@ public class TestDmaapConsumerImpl {
         assertEquals("secret", props.getProperty("password"));
     }
 
-    
+    @Ignore("test is taking 130 sec")
     @Test
     public void testFetch() {
        DmaapConsumerImpl consumer = new DmaapConsumerImpl(hosts, topic, group, id, key, secret);