Timeline for How to E2E test handling of an unknown error in a client-server application?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2023 at 18:34 | comment | added | gnasher729 | That’s a case for mocking. With mocking you can get any errors. However, you can’t have case specific handling or fix the problem. You can just put everything that is unexpected into the category “unexpected error”. | |
| Nov 9, 2022 at 21:02 | comment | added | Greg Burghardt | @Spenhouet: by utilizing black-box testing. You basically guess. You try things out. You experiment on your system. You can also utilize white-box testing, which affords you some knowledge of internals so you can simulate things like, what if a database operation succeeds but a subsequent file operation fails? You will need to research testing strategies, with a focus on black and white-box testing. | |
| Nov 9, 2022 at 20:31 | comment | added | Spenhouet | Let's say we cannot find any new unknown errors (because we fixed them all). Then how are we going to test the "unknown error handling"? | |
| Nov 9, 2022 at 20:18 | history | answered | Greg Burghardt | CC BY-SA 4.0 |