This is a small scale app by any sensible standards and probably not that complex compared to what's being routinely deployed by 2-3 man development teams in th

This is a small scale app by any sensible standards and probably not that complex compared to what's being routinely deployed by 2-3 man development teams in the world of business. i routinely handle spreadsheets with larger datasets and more complexity then whats involved here. There is books written on how to test an new system/feature but in general you have 3 stages: The first is an automated internal integrity test(sometimes called unit test) where you throw mock data at the systems independent component, in order to test for known classes of edge cases and race conditions. The second step is implementation where the ops team tries to yank network and hardware resources away form underneath the app until something breaks in order to see if it fails in a sensible way that don't lead to irrecoverable data corruption. The third stage is acceptance testing which on proprietary solutions is often the only one the end user is 110% in control of where you both test the app with actual user performing standard procedures and an team of specialist trying and break it using whatever knowledge they have on the systems design. All tree stages have it's own skill set and is often performed by different teams and it's not uncommon to see specialist companies brought in doing part of the QA process for really important new systems but for the most part the entire things just fade into the the daily routine as an newer ending feedback loop.