4 ms·
I think part of the question should be, why is there no QA or test that catches this? It's one thing to be slopware, but why didn't anything run a test that cat
by altcognito 4mo ago
I think part of the question should be, why is there no QA or test that catches this? It's one thing to be slopware, but why didn't anything run a test that catches this?
- theowaway213456 4mo agoEvery time you write a test that handles some data, you write an assertion about how much data is handled? Come on, this is such an easy thing to forget to test. Don't act like there is some magical testing strategy that would have caught this
- altcognito 4mo agoI'll acknowledge that this is probably not likely to get caught. Integration testing could/should catch this, especially for a client side app. A simple constraints is a good thing. "Our app shouldn't use more than 50mb of ram, or use 3gb of disk space."
- cute_boi 4mo agoload testing definitely should have caught this issue.
- tomjakubowski 4mo agoThe most likely way I think you'd catch this in a test would be by accident, running some kind of long-running integration test for other purposes, and then finding the disk gets filled up in CI (or on a developer machine).
- java-man 4mo agowhat QA?
- cute_boi 4mo agoQuality assurance testing....