OpenSTF @ Test Engineers' Meetup #3

- What is OpenSTF?
- Why use OpenSTF?
- How's the project doing?
- Future direction

August 28th, 2018 @ Rakuten Crimson House

1. OpenSTF Test Engineers Meetup #3 Tokyo August 28th, 2018 @ Rakuten Crimson House
2. Created OpenSTF at CyberAgent in 2013 Who are we? Gunther Brunner ブルンナー・グンタ @gunta85 Simo Kinnunen キンヌネン・シモ @sorccu
3. Agenda • What is OpenSTF? • Why use OpenSTF? • How's the project doing? • Future direction
4. What is OpenSTF?
6. What is OpenSTF? • OpenSTF is an on-premises, free, open source device management platform • Created at CyberAgent, open sourced in 2015 • Apache 2.0 license • 7,700+ stars on GitHub • Compare to e.g. AWS Device Farm, Google Cloud Test Lab
7. What does it do? • Provides effortless remote access to your test devices • Remote control for manual testing and debugging • Remote monitoring and recovery of test runs • Integrates with automation and development tools • Appium, Jenkins, Android Studio, ADB, etc.
8. What it looks like
9. How you use it
10. How you use it
11. Meet the team @sorccu Tokyo @gunta Tokyo @vbanthia Tokyo @thinkhy Beijing @koral-- Poland
12. Why use OpenSTF?
13. Why use OpenSTF? • Cost reduction: fewer devices needed • Scales to thousands of devices • Supports almost any device • Runs on commodity hardware • Easy to use (though perhaps not to set up...) • Open source
14. How's the project doing?
15. Still growing https://github.com/s0ph1e/star-history
16. Companies using OpenSTF
17. Companies using OpenSTF
18. Featured on Google Web Fundamentals “Best Practices”
19. Popular in China • Because it works On-Premise
 it is notably popular in China
20. Not much new development lately - why?
21. Time spent on the project 2013-2015 Code Mon 10 AM 19 PM Code Code Code Code Code Code Tue Wed Thu Fri Sat Sun Email Email Email Email Email Email Email Writing code Answering emails Email
22. ... Time spent on the project 2016-2018 ... Mon 10 AM 19 PM Tue Wed Thu Fri Sat Sun Email Email Email ... ... ... Email Email Writing code Answering emails Code Code Email
23. Prohibitive cost • All manufacturers are now making expensive flagship devices • More Android versions - need a few devices for each version, so one or two development devices are not enough • Making sure that old versions don't break is time consuming
24. Few contributions • Companies like to keep their changes to themselves • Low interest in sponsorship
25. Still… Why Open-Source?
26. Open as much as possible 競争⼒力力
 レベル カテゴリー 事例例 開発コスト 運⽤用コスト 普及率 プルリク
 相乗効果 ロックイン
 リスク レガシー化
 リスク 365/24
 運⽤用体制 レベル 1 部⾨門内基盤 Hogehoge 0 基盤側 プロダクト側 ❌ 低 ⾼高 ❌ レベル 2 社内 GHE Hogehoge 1 基盤側 プロダクト側 ⭕ 低 中 レベル 3 社内 SaaS Hogehoge 2 基盤側 基盤側 ❌ 中 中 ⭕ レベル 4 社外 OSS OpenSTF 基盤側 プロダクト側 ⭕ 無 中 レベル 5 社外 SaaS Mackerel 基盤側 基盤側 ❌ ⾼高 低 ⭕ レベル 6 社外OpenSaaS Kubernetes
 Redis 基盤側 基盤側 ⭕ 無 無 ⭕
27. Future direction
28. Things we want to do • iOS support • Faster and more efficient screen capture with WebRTC • Improved reliability
29. Q & A Keep up to date at https://github.com/openstf/stf Stars are appreciated ;)