stuck on a weird Test Automation edge case
i keep hitting this in Test Automation and the docs skip the failure path. is the miss supposed to throw or just return null?
about 1 month ago

Automated checks for UI, API, and regression.
i keep hitting this in Test Automation and the docs skip the failure path. is the miss supposed to throw or just return null?
we compared the old Test Automation setup with the new one on the same traffic. latency dropped, on call pages did not. curious what other people measured besides the demo benchmark.
See more →