iluwatar#643 Fix flaky tests for throttling pattern

Author: christophercolumbusdog

throttling/src/test/java/com/iluwatar/throttling/B2BServiceTest.java

@@ -22,29 +22,27 @@
  */
 package com.iluwatar.throttling;
 
-import com.iluwatar.throttling.timer.ThrottleTimerImpl;
 import com.iluwatar.throttling.timer.Throttler;
-import org.junit.jupiter.api.Disabled;
 import org.junit.jupiter.api.Test;
 
-import static org.junit.jupiter.api.Assertions.assertTrue;
+import static org.junit.jupiter.api.Assertions.assertEquals;
 
 /**
  * B2BServiceTest class to test the B2BService
  */
 public class B2BServiceTest {
 
-  @Disabled
   @Test
   public void dummyCustomerApiTest() {
     Tenant tenant = new Tenant("testTenant", 2);
-    Throttler timer = new ThrottleTimerImpl(100);
+    // In order to assure that throttling limits will not be reset, we use an empty throttling implementation
+    Throttler timer = () -> {};
     B2BService service = new B2BService(timer);
 
     for (int i = 0; i < 5; i++) {
       service.dummyCustomerApi(tenant);
     }
     long counter = CallsCount.getCount(tenant.getName());
-    assertTrue(counter == 2, "Counter limit must be reached");
+    assertEquals(2, counter, "Counter limit must be reached");
   }
 }