Beyond the "Error 404" Making Better Error Messages

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Beyond the "Error 404" Making Better Error Messages

sogeg
Hi everyone,

I’ve been working on a side project—a custom inventory app for jewelry sellers—and I’m obsessed with the "feel" of the user interface.
'
I hate it when apps just vanish or freeze when they encounter a bad file. I want to build a system that tells the user exactly what went wrong in a friendly way.

To get the code right, I need to feed it a bunch of broken data to see if my try-catch blocks actually trigger the way I planned in my logic. Is there a specific resource or method you recommend to test error handling with corrupted files?

thanks in advance.