You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1023,6 +1023,7 @@ beforeEach(() => {
1023
1023
});
1024
1024
});
1025
1025
```
1026
+
1026
1027
</details>
1027
1028
<br/>
1028
1029
@@ -1063,12 +1064,12 @@ beforeEach(() => {
1063
1064
1064
1065
## ⚪ ️2.11 Check integrations corner cases and chaos
1065
1066
1066
-
:white_check_mark:**Do:** When checking integrations, go beyond the happy and sad paths. Check not only errored responses (e.g., HTTP 500 error) but also network-level anomalies like slow and timed-out responses. This will prove that the code is resilient and can handle various network scenarios like taking the right path after a timeout, has no fragile race conditions, and contains a circuit breaker for retries. Reputable interceptor tools can easily simulate various network behaviors like hectic service that occasionally fail. It can even realize when the default HTTP client timeout value is longer than the simulated response time and throw a timeout exception right away without waiting
1067
+
:white_check_mark:**Do:** When checking integrations, go beyond the happy and sad paths. Check not only error responses (e.g. HTTP 500 error) but also network-level anomalies like slow and timed-out responses. This will prove that the code is resilient and can handle various network scenarios like taking the right path after a timeout, has no fragile race conditions, and contains a circuit breaker for retries. Reputable interceptor tools can easily simulate various network behaviors like hectic service that occasionally fail. It can even realize when the default HTTP client timeout value is longer than the simulated response time and throw a timeout exception right away without waiting
1067
1068
1068
1069
1069
1070
<br/>
1070
1071
1071
-
❌ **Otherwise:** All your tests pass, it's only the production who will crash or won't report errors correctly when 3rd parties send excpetional responses
1072
+
❌ **Otherwise:** All your tests pass, it's only the production who will crash or won't report errors correctly when 3rd parties send exceptional responses
1072
1073
1073
1074
<br/>
1074
1075
@@ -1198,7 +1199,7 @@ test("When flagging to show only VIP, should display only VIP members", () => {
1198
1199
1199
1200

0 commit comments