Testing of new features in software project

The logic of new features on both platforms is also the same, since one code is written: testing complex processes inside the application comes down to testing them on one platform and confirming them on another. We conduct a full cycle of activities on one platform: we do exploratory testing, feature runs, smoke / sanity / full, analyze feedback. After that, it remains only to confirm the quality by exploratory testing on another platform. This approach saves the time of testing the logic by about 1.3 times.

Example

Suppose that analysts, while testing events, noticed a situation: according to the TOR, the event should be sent to the appropriate analytics system, but it is not tracked. Such a gap in the logic clearly indicates that the event will not be sent on both platforms.

Having fixed the bugs and made sure in various scenarios that the collection of analytics in the application works correctly on one of the platforms (for example, iOS), we can assume with greater confidence that we will not encounter a bug on another platform (Android) associated with the track of an extra event or the absence of the necessary event in the analytics system.