2 ms·
The complexity of our application necessitates that our business owners do a lot of the final integration testing. It also requires that our product owners han
by bob1029 5y ago
The complexity of our application necessitates that our business owners do a lot of the final integration testing.
It also requires that our product owners handle a large part of the implementation & QA efforts.
For our application, a single piece of code might be reused 40 different ways across 100 different customers based on configuration-time items.
To ask a developer to figure out why something is broken would be a fool's errand for us. Only with the aid of trace files & configuration references are we able to perform RCA and clean up an issue from live usage. For us, 99% of the time it is a configuration thing (either on our end or some 3rd party system). If the code works for 99 clients and 39 other configurations, it might be your client+config that is wrong, not the code.
- ukd1 5y agoWhat do you use to plan it or otherwise manage the process? Is it all manual?
- bob1029 5y agoEssentially yes. We are trying to move to a hybrid model where we can send excel workbooks to the customer for completion, and then directly import these into the system. This would get us ~80% of the way there. One huge upside with configuration is that it can be copied really easily. If you have a model customer that is very similar to others, you can use it as a starting point and save 99% of the work effort.
- ukd1 5y agoMakes sense. Did y'all try to automate any of it? I've seen situations where things are highly-configurable, and massive at the same time - mostly in the medical industry. Test plans are hard due to interactions between config being highly-complex. No sense testing all of the setups, as not all are used or would even make sense.