Change Details

One area that we need to improve is to start test performance on real devices. There's is a short term goal and a long term. Lets start with the long term: * Every code change should automatically be tested on a real device. Short term goal: * Make it easy to for a engineer to test if specific changes have an impact on performance on real devices. There are some interesting reads on how [Facebook does it](https://code.facebook.com/posts/924676474230092/mobile-performance-tooling-infrastructure-at-facebook/) and a [video](https://developers.facebook.com/videos/f8-2016/mobile-performance-tools-at-facebook/). What it means is that we need to have a device lab in house (= devices that we as engineers can use automatically). There's a couple of different ways to do it: * [WebPageTest](http://www.webpagetest.org/), it support real devices but do we need to run Windows? * [Selendroid](http://selendroid.io/) that is used by Ebay and Facebook. * [Appium](http://appium.io/) * Could [STF](https://github.com/openstf/stf) be something for us? * Our own solution using Selenium, I've made a POC during the reading offsite, I'll put that on Github the coming days. It's a lot of work to make this happen and it is something we need to do. I'll add more text to this epic the coming weeks.

One area that we need to improve is to start test performance on real devices. There's is a short term goal and a long term. Lets start with the long term: * Every code change should automatically be tested on a real device. Short term goal: * Make it easy to for a engineer to test if specific changes have an impact on performance on real devices. There are some interesting reads on how [Facebook does it](https://code.facebook.com/posts/924676474230092/mobile-performance-tooling-infrastructure-at-facebook/) and a [video](https://developers.facebook.com/videos/f8-2016/mobile-performance-tools-at-facebook/). What it means is that we need to have a device lab in house (= devices that we as engineers can use automatically). There's a couple of different ways to do it: * [WebPageTest](http://www.webpagetest.org/), it support real devices but do we need to run Windows? * [Selendroid](http://selendroid.io/) that is used by Ebay and Facebook. * [Appium](http://appium.io/) * Could [STF](https://github.com/openstf/stf) be something for us? * [vs-mobile](https://github.com/soulgalore/vs-mobile) - I've made a POC during the reading offsite. It's a lot of work to make this happen and it is something we need to do. I'll add more text to this epic the coming weeks.

One area that we need to improve is to start test performance on real devices. There's is a short term goal and a long term. Lets start with the long term: * Every code change should automatically be tested on a real device. Short term goal: * Make it easy to for a engineer to test if specific changes have an impact on performance on real devices. There are some interesting reads on how [Facebook does it](https://code.facebook.com/posts/924676474230092/mobile-performance-tooling-infrastructure-at-facebook/) and a [video](https://developers.facebook.com/videos/f8-2016/mobile-performance-tools-at-facebook/). What it means is that we need to have a device lab in house (= devices that we as engineers can use automatically). There's a couple of different ways to do it: * [WebPageTest](http://www.webpagetest.org/), it support real devices but do we need to run Windows? * [Selendroid](http://selendroid.io/) that is used by Ebay and Facebook. * [Appium](http://appium.io/) * Could [STF](https://github.com/openstf/stf) be something for us? * Our own solution using Selenium,* [vs-mobile](https://github.com/soulgalore/vs-mobile) - I've made a POC during the reading offsite, I'll put that on Github the coming days. It's a lot of work to make this happen and it is something we need to do. I'll add more text to this epic the coming weeks.