gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

#643 Fix flaky tests for throttling pattern

Browse Source
This commit is contained in:
Christian Cygnus 2018-05-25 22:26:35 -05:00
parent d7893c1fc2
commit 4ab46c7fcb
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
throttling/src/test/java/com/iluwatar/throttling/B2BServiceTest.java
View File

@ -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");
}
}