Tweet
Tweet

Slide 1

Slide 1 text

@mtsmfm Rails System Test on Docker

Slide 2

Slide 2 text

松島 史秋 GitHub, Twitter @mtsmfm Web Developer

Slide 3

Slide 3 text

https://www.quipper.com/

Slide 4

Slide 4 text

https://ninirb.github.io

Slide 5

Slide 5 text

https://www.meetup.com/ja-JP/GraphQL-Tokyo/

Slide 6

Slide 6 text

この発表で 伝えたいこと

Slide 7

Slide 7 text

Docker を 使うと 楽できる

Slide 8

Slide 8 text

開発環境に Docker を 使おう

Slide 9

Slide 9 text

1. Rails System Test とは 2. Docker を使うとどうなるか 3. Docker とのくっつけかた

Slide 10

Slide 10 text

Rails System Test とは

Slide 11

Slide 11 text

- Rails 5.1 で入った - Capybara を使う - DB cleaner の類が 要らない

Slide 12

Slide 12 text

http://weblog.rubyonrails.org/2017/4/27/Rails-5-1-final/

Slide 13

Slide 13 text

- Rails 5.1 で入った - Capybara を使う - DB cleaner の類が 要らない

Slide 14

Slide 14 text

require "test_helper" class ApplicationSystemTestCase < ActionDispatch::SystemTestCase driven_by :selenium, using: :chrome, screen_size: [1400, 1400] end require "application_system_test_case" class PostsTest < ApplicationSystemTestCase test "visiting the index" do visit posts_url assert_selector "h1", text: "Post" end end

Slide 15

Slide 15 text

require "test_helper" class ApplicationSystemTestCase < ActionDispatch::SystemTestCase driven_by :selenium, using: :chrome, screen_size: [1400, 1400] end require "application_system_test_case" class PostsTest < ApplicationSystemTestCase test "visiting the index" do visit posts_url assert_selector "h1", text: "Post" end end

Slide 16

Slide 16 text

- Rails 5.1 で入った - Capybara を使う - DB cleaner の類が 要らない

Slide 17

Slide 17 text

Test code (minitest) Rails (puma) DB Connection Connection

Slide 18

Slide 18 text

- database_cleaner - transaction - truncation - database_rewinder - 賢い truncation

Slide 19

Slide 19 text

https://gist.github.com/josevalim/470808

Slide 20

Slide 20 text

Test code (minitest) Rails (puma) DB Connection

Slide 21

Slide 21 text

https://github.com/rails/rails/pull/28083

Slide 22

Slide 22 text

https://github.com/rails/rails/pull/28083/files?diff=unified

Slide 23

Slide 23 text

https://speakerdeck.com/eileencodes/railsconf-2017- building-the-new-rails-system-test-framework

Slide 24

Slide 24 text

1. Rails System Test とは 2. Docker を使うとどうなるか 3. Docker とのくっつけかた ✓

Slide 25

Slide 25 text

Docker を使うとどうなるか

Slide 26

Slide 26 text

Test code (minitest) Rails (puma) DB Connection

Slide 27

Slide 27 text

Test code (minitest) Rails (puma) DB Selenium Browser Host

Slide 28

Slide 28 text

Test code (minitest) Rails (puma) DB Selenium Browser (chrome) web db chrome

Slide 29

Slide 29 text

$ brew install chromedriver

Slide 30

Slide 30 text

$ brew install chromedriver $ brew install postgresql $ brew install rbenv ...

Slide 31

Slide 31 text

$ brew install chromedriver $ brew install postgresql $ brew install rbenv ...

Slide 32

Slide 32 text

必要なもの Docker for Mac docker-sync 以上!

Slide 33

Slide 33 text

1. Rails System Test とは 2. Docker を使うとどうなるか 3. Docker とのくっつけかた ✓ ✓

Slide 34

Slide 34 text

Test code (minitest) Rails (puma) DB Selenium Browser (chrome) web db chrome

Slide 35

Slide 35 text

version: '2' services: web: build: . environment: - DATABASE_URL=postgres://postgres:@db - PORT=3000 - HOST=0.0.0.0 tty: true stdin_open: true ports: - 3000:3000 depends_on: - db - chrome volumes: - .:/app chrome: image: selenium/standalone-chrome-debug ports: - 5900:5900 db: image: postgres:9.5.4

Slide 36

Slide 36 text

require "test_helper" require "socket" class ApplicationSystemTestCase < ActionDispatch::SystemTestCase driven_by :selenium, using: :chrome, screen_size: [1400, 1400], options: {url:"http://chrome:4444/wd/hub"} def setup host! "http://#{IPSocket.getaddress(Socket.gethostname)}" super end end

Slide 37

Slide 37 text

require "test_helper" require "socket" class ApplicationSystemTestCase < ActionDispatch::SystemTestCase driven_by :selenium, using: :chrome, screen_size: [1400, 1400], options: {url:"http://chrome:4444/wd/hub"} def setup host! "http://#{IPSocket.getaddress(Socket.gethostname)}" super end end

Slide 38

Slide 38 text

Test code (minitest) Rails (puma) DB Selenium Browser (chrome) web db chrome

Slide 39

Slide 39 text

https://github.com/rails/rails/pull/28341

Slide 40

Slide 40 text

require "test_helper" require "socket" class ApplicationSystemTestCase < ActionDispatch::SystemTestCase driven_by :selenium, using: :chrome, screen_size: [1400, 1400], options: {url:"http://chrome:4444/wd/hub"} def setup host! "http://#{IPSocket.getaddress(Socket.gethostname)}" super end end

Slide 41

Slide 41 text

Test code (minitest) Rails (puma) DB Selenium Browser (chrome) web db chrome

Slide 42

Slide 42 text

https://github.com/rails/rails/pull/28644

Slide 43

Slide 43 text

$ open vnc://:secret@localhost:5900

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

ヘッドレスっぽく使いつつ 直接操作もできる!

Slide 46

Slide 46 text

この構成をとっておけば Browser Stack なども 導入しやすい

Slide 47

Slide 47 text

100.times do |i| test "visiting the index #{i}" do visit posts_url assert_selector "h1", text: "Post" end end ブラウザ 時間 Chrome 25.269699s Headless Chrome 16.881625s PhantomJS 12.243397s https://github.com/mtsmfm/rails-system-test-example/pull/2

Slide 48

Slide 48 text

※ Chrome unstable にしつつ cap-add SYS_ADMIN しないと 動かなかった https://github.com/mtsmfm/rails-system-test-example/pull/2/files#d iff-1f904fb99929e223c9e3d8171b05d87e

Slide 49

Slide 49 text

まとめ - Docker を使うとホストに いれるものが減る - ヘッドレスっぽくありつつも VNC で入れて便利 - とはいえ --headlessの方が速い - どっちにしろ Docker で動かせる - CI だと --headless にするといい? - 作り始めるときは Docker 上で

Slide 50

Slide 50 text

Credits Background pattern from subtlepatterns.com