4 ms·
Test Evidence Chaos After a Crash with Error Code ER5001
During one of our QA tests, the software completely crashed, throwing the error code ER5001. It caught us off guard because the crash wiped all unsaved progress and logs. We had to scramble to recreate the test scenario manually, which took hours. Capturing proper test evidence for this was a nightmare screenshots, steps, and logs were scattered. Has anyone faced similar issues and found tools to streamline test evidence collection, especially after unexpected crashes ?
- cebert 2y agoFirst this type of post should have an ask HN prefix. Secondly, there aren’t nearly enough details about this very specific issue.
- Demonnslayerrr 2y agoFacing issues with using the platform , Here are the details I am trying build a financial analytics platform. The software is designed to process large datasets for risk assessment and our test scenario involved uploading a custom CSV file with over 10,000 rows of transactional data to evaluate how the system handled complex financial patterns. But as soon as we attempted to run a query on the same it crashed!
- Padelictrumpet 2y agoI completely understand your frustration unexpected crashes like this can be a nightmare, especially when you lose valuable progress and logs. It sounds like your current setup lacks a robust mechanism to capture test evidence during such critical failures. If you haven't already, ensure you're logging both system-level metrics (CPU, memory) and application-level actions (query execution plans, data validation outputs). These, combined with a tool like Autoflow, can make debugging much more manageable.