I'm wondering if anyone could help me with a strategy to ensure correct coverage for upcoming releases. A little about our setup...
We have multiple iOS apps released across different European regions. These all share the same codebase but point to different urls, depending on the scheme selected, which handles localisation for that region. That's the only difference between them at the moment. We've released them all concurrently and each region has been tested and there have been no issues.
My worry is for upcoming releases. Say, for example, we see an issue in the Italian app (e.g. truncated text when Italian language is used). We only want to release the fix for the Italian scheme so we test that and release. Our codebase is updated with that fix, and therefore it's updated for all our other regions, but they haven't been tested (because they've not been released).
I can envisage problems with this strategy. Say, in 6 months, we want to release a fix for the French app. Well, in those 6 months, the codebase could have been updated with a number of regional releases to that point. Very hard to track, even harder to track down tests related to each release.
Can anyone suggest a strategy to deal with this issue? When releasing one region, should all regions be tested at that point, despite not all been released? Any strategy on tracking a complete list of changes (e.g. through branches or tags) so if I am beginning work on a new release, I can first run a regression on releases up to that point to make sure it's okay.
I have no automation just yet but will do in the next few months. Thanks everyone for reading, and hopefully someone can offer some insight.