Change Details

Let's collect real traces from a phone before we do the change and after we did the change. I'm thinking of two different user scenarios: * direct access to a wikipedia article using the desktop domain, using a mobile phone * click on a wikipedia link on Google search result, using a mobile phone. Lets do it on https://it.wikipedia.org (the change happen 8-11 September) and then on https://en.wikipedia.org (22.-26 September). See the subtasks. AC: * [] Add the test configuration and scripts so its reproducible.

One of the reasons (except that almost all other web entities removed the .m domain) is that Google sometime ago changed so in the search result, they always link to the domain without the m. That means when you are on mobile and click on the link in the search at Google you will get an extra redirect to the correct domain (instead of us handle it internally). By collecting data how it works today and collect data after the change we will be able to prove that it works the way we want (no redirect). We do test some of this functionality in the performance monitoring but it uses emulated devices (a desktop machine that says it is a mobile device) and we need verify that it really works so having data from real mobile phones is more safe. Let's collect real traces from a phone before we do the change and after we did the change. I'm thinking of two different user scenarios: * direct access to a wikipedia article using the desktop domain, using a mobile phone * click on a wikipedia link on Google search result, using a mobile phone. Lets do it on https://it.wikipedia.org (the change happen 8-11 September) and then on https://en.wikipedia.org (22.-26 September). See the subtasks. AC: * [] Add the test configuration and scripts so its reproducible.

One of the reasons (except that almost all other web entities removed the .m domain) is that Google sometime ago changed so in the search result, they always link to the domain without the m. That means when you are on mobile and click on the link in the search at Google you will get an extra redirect to the correct domain (instead of us handle it internally). By collecting data how it works today and collect data after the change we will be able to prove that it works the way we want (no redirect). We do test some of this functionality in the performance monitoring but it uses emulated devices (a desktop machine that says it is a mobile device) and we need verify that it really works so having data from real mobile phones is more safe. Let's collect real traces from a phone before we do the change and after we did the change. I'm thinking of two different user scenarios: * direct access to a wikipedia article using the desktop domain, using a mobile phone * click on a wikipedia link on Google search result, using a mobile phone. Lets do it on https://it.wikipedia.org (the change happen 8-11 September) and then on https://en.wikipedia.org (22.-26 September). See the subtasks. AC: * [] Add the test configuration and scripts so its reproducible.