Introduction of mercari SET team

A2a2d96ab7fae2ccc4fb8e88cc7f8698?s=47 masudak
March 17, 2017

Introduction of mercari SET team

A2a2d96ab7fae2ccc4fb8e88cc7f8698?s=128

masudak

March 17, 2017
Tweet

Transcript

  1. Introduction of mercari SET team ICST meetup @masudaK 2017/03/17

  2. mercari

  3. mercari • A customer to customer marketplace app for iOS,

    Android and Web • You can sell anything(legal) • You can buy anything • 60 million downloads in JP and US • Now released in UK
  4. None
  5. None
  6. mercari • Founded: 2013/02/01 • Meaning: “Market” in Latin •

    Office: Tokyo, Sendai, Fukuoka, San Francisco, Portland and London • People: about 400
  7. SET (Software Engineer in Test)

  8. SET • Members: 5 • Started: 2016/10 • Mission: ◦

    Improve product quality and developer productivity through engineering
  9. Approach • product quality: ◦ By automating E2E tests ◦

    By creating flexible testing environments ◦ By introducing new tools for test case management • developer productivity ◦ By creating development environment with single command
  10. Me

  11. Me • HN: @masudaK on Twitter • Position: SET in

    mercari • Joined: 2016/04/15 • Before: SRE • Now: SET
  12. Recently

  13. None
  14. None
  15. None
  16. Explosion of new employees

  17. None
  18. None
  19. None
  20. Explosion of new regions

  21. Automation is a MUST

  22. Our job

  23. One command dev environment

  24. Ideology • Easy getting started • Easy tracing error •

    Disposable • Simple Architecture • Not only for engineers • Here to help with anything
  25. Design • By using Docker for Mac and docker-compose •

    By registering user domains on local DNS • By dividing data with data container
  26. Images

  27. Execute only “make init”

  28. Then you can access

  29. https://masuda-api-us.your-domain.com

  30. One click QA environments

  31. Ideology • Have own environments for QA • Disposable •

    Easy to create(1min) • Easy to deploy own topic branch
  32. Design • The system for QA • Mainly created by

    docker-compose • on GCP • Closest Instance by geo load balancer • Using oauth2-proxy as auth • Using GCP snapshot and ansible • Using rundeck for job management
  33. None
  34. Access admin url

  35. None
  36. Choose your instance

  37. Choose your topic branch

  38. Just click “build” button

  39. None
  40. Anyone can use their own QA env

  41. Automate E2E tests

  42. Current environments XCUITest iOS Android

  43. Problem one • follow up the changes of UI •

    catch up the differences of A/B tests
  44. To keep coverage is difficult

  45. Problem two • tell the product team how automation will

    improve • their development cycle • their product quality
  46. To publish outputs is so important

  47. Problem thee • choice the valid tool and language •

    management for test case (ex: Excel, TestRail and so on) • platform for tests (ex: Device Farm, STF and so on) • programming language (ex: Ruby, Python, Swift and so on)
  48. We have lots of challenges

  49. We need more engineers

  50. https://www.mercari.com/jp/jobs/ https://www.wantedly.com/projects/62657

  51. Thank you