We continue writing our cycle. Parts one and two are available on our Medium. If you haven’t read this far, go ahead. This knowledge will help you deal with it with confidence. For those who are already know the cycle, let us remind you of the theses of the previous article:
- We have considered the structure of experiments: the configuration table, the experiment table, the testing process itself
- Described the chronology of problems
- Analyzed the hypothesis about the influence of device hardware on deep link processing
Hypothesis 1: Different devices — BUSTED.
The device (hardware part) does NOT affect Deep Link processing.
We have examined in detail how the Android OS version affects deep link processing
Hypothesis 2. Different Android versions is BUSTED.
Android OS version does NOT affect Deep Link processing.
Today we are going to deal with two more issues related to OS shells and the application from which deeplink is opened.
At the end of the previous article, we formulated hypotheses 3 and 4:
Hypothesis 3. Different OS shells.
Android OS shell affects the performance of Deep Link.
Hypothesis 4. Application.
The application from which the link is opened affects Deep Link.
Today we’re going to break down some interesting examples that will set the stage. Let’s get started!
Problem ???3. Different shells
Different OS shells. Deep link processing was different on different Android shells
Let’s describe the conditions under which the problem is reproduced:
Config X-1. One UI configuration
Config Y-1. Vanila configuration
On both devices, open Gmail, send yourself an email with the link domain1.domain2.ru/landing, receive it, open it, click on it.