Tweet
Tweet

Slide 1

Slide 1 text

OpenSTF Test Engineers Meetup #3 Tokyo August 28th, 2018 @ Rakuten Crimson House

Slide 2

Slide 2 text

Created OpenSTF at CyberAgent in 2013 Who are we? Gunther Brunner ブルンナー・グンタ @gunta85 Simo Kinnunen キンヌネン・シモ @sorccu

Slide 3

Slide 3 text

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

Slide 4

Slide 4 text

What is OpenSTF?

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

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

Slide 7

Slide 7 text

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.

Slide 8

Slide 8 text

What it looks like

Slide 9

Slide 9 text

How you use it

Slide 10

Slide 10 text

How you use it

Slide 11

Slide 11 text

Meet the team @sorccu Tokyo @gunta Tokyo @vbanthia Tokyo @thinkhy Beijing @koral-- Poland

Slide 12

Slide 12 text

Why use OpenSTF?

Slide 13

Slide 13 text

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

Slide 14

Slide 14 text

How's the project doing?

Slide 15

Slide 15 text

Still growing https://github.com/s0ph1e/star-history

Slide 16

Slide 16 text

Companies using OpenSTF

Slide 17

Slide 17 text

Companies using OpenSTF

Slide 18

Slide 18 text

Featured on Google Web Fundamentals “Best Practices”

Slide 19

Slide 19 text

Popular in China • Because it works On-Premise
 it is notably popular in China

Slide 20

Slide 20 text

Not much new development lately - why?

Slide 21

Slide 21 text

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

Slide 22

Slide 22 text

... 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

Slide 23

Slide 23 text

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

Slide 24

Slide 24 text

Few contributions • Companies like to keep their changes to themselves • Low interest in sponsorship

Slide 25

Slide 25 text

Still… Why Open-Source?

Slide 26

Slide 26 text

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 基盤側 基盤側 ⭕ 無 無 ⭕

Slide 27

Slide 27 text

Future direction

Slide 28

Slide 28 text

Things we want to do • iOS support • Faster and more efficient screen capture with WebRTC • Improved reliability

Slide 29

Slide 29 text

Q & A Keep up to date at https://github.com/openstf/stf Stars are appreciated ;)