Hi Deep,
Good question - I am not aware of a particular approach/strategy, but I would say it should be treated in the same manner as also testing other custom developers, enhancements etc. Irrespective if it is a Fiori-app, classical report, Interface etc.
In general, I would recommend to automate your testing in general. There are tools around, which are even to some extent integrated into your companies SAP license. Tricentis from Tosca is one example, but there are probably much more around. The idea is, that you have a recorded script, which steps should beexecuted for your test case, and then, you can simply re-run them after upgrades or any other changes that you thing could have an effect. Reducing manual effort and also source of mistakes, increasing reproducibility etc.
Also, what you could look up is the so called “test driven development”, again, nothing particular to Fiori-apps itself.
Hope that helps,
BR Aleks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.