How to Build an Appium Continuous Testing Pipeline

Size: px

Start display at page:

Download "How to Build an Appium Continuous Testing Pipeline"

Arnold Clark
5 years ago
Views:

1 How to Build an Appium Continuous Testing Pipeline Step-by-Step Tutorial November, 2017

2 Today s speakers Guy Arieli, CTO, Experitest Ruth Zamir Marketing Director Experitest

3 01 Why do we need continuous testing? 15 min Agenda 02 The continuous testing environment 5 min 03 Step-by-step demo 30 min 04 Q&A 10 min 3

4 Digital transformation impacts business Customer empowerment Digital is a key survival strategy Frequent app releases (mobile: 2 weeks, web: daily, even hourly) 4 R&D organizations under pressure more, faster, better

5 Unique mobile market characteristics Device matrix large and constantly evolving Fast technology innovation & complex integration (Alexa/Siri, IoT, AR.. High cost of error - App/play stores create a distribution gap that makes rollback impossible Scope * Velocity * Risk 5

6 SDLC Paradigm shift Speed, agility and risk reduction Agile DevOps CI/CD Develop smaller chunks - we will probably change our mind get your team talking make sure you didn t break anything 6

7 What is Continuous Integration? a software development practice where members of a team integrate their work frequently... Each integration is verified by an automated build to detect integration errors as quickly as possible.

8 There is no Continuous Integration without Continuous Testing

9 The estimated* impact of a shortened feedback loop R&D productivity will increase from 10% to 35% since more time will be invested on Dev-test activities Root cause analysis 25% R&D productivity - 1 week feedback Administration 5% Dev-test 10% Project related 15% Administration 5% Root cause analysis 13% R&D productivity - 1 hour feedback Dev-test 35% Bug reproduction 13% Bug reproduction 25% Context switching 20% Context switching 14% Project related 20% * Data source: Experitest customers

10 Rapid feedback significantly increases R&D effectiveness 60 R&D Effectiveness week 1 day 6 hours 2 hours 1 hour 1 minute Time to feedback

11 The dev-test process Epic Story thinning Prototype Acceptance Criteria Functional Spec Product Owner Analyst Product Owner Analyst Designer Analyst Tester Test Engineer Dev Engineer Showcase / Demo Sign-off Acceptance testing Automated testing Build & Deploy Code (incl. White box Test) Product Owner Tester Dev & Test Engineer DevOps Engineer Dev & Test Engineer CI/CD cycle

12 Continuous testing in mobile - implications High scales simultaneous testing of different use cases, devices and network conditions Highly stable test suites Test environment management requires IT / Security expert Rapid result analysis and actionable feedback 12

13 01 Why do we need continuous testing? Agenda 02 The continuous testing environment 03 Step-by-step demo 04 Q&A 13

14 The Continuous Testing process Test Engineer Development Engineer Commit tests 1 Commit app code Pull test 4 source Trigger build build 6 Load app 7 Trigger test to cloud execution 8 Consolidate test results test report Continuous Integration Build test 5project 2 Pull app source 3 Build app 9 Version approved? 10 Debug / update test suite no yes

15 Today s demo environment Pre-prepared Tools used What we will do Appium tests TestNG framework Jenkins server Appium* Studio for Eclipse Eclipse* Jenkins* Git Gradle Experitest Digital Device Lab Experitest Reporter Build Application (Jenkins) Pull tests from Git and build test project (Jenkins + Gradle) Upload application to the cloud - Jenkins (shell script) Run Tests (Jenkins + Digital Device Lab) Link test results to Jenkins * Any test framework, IDE and CI tools can be used

16 01 Why do we need continuous testing? Agenda 02 The continuous testing environment 03 Step-by-step demo 04 Q&A 16

17 Demo Configuration and setup 17

18 Executing from Jenkins 18

19 Recap What we did Used CI server to build an application from repository Used CI server to build a test project from repository Used CI to upload application to digital device lab Used CI and digital device lab to installed application numerous devices and run tests in parallel on Used Reporter to link test results to CI and analyzed test results Tools / frameworks used Appium* TestNG* Eclipse* Jenkins* Git Gradle Appium Studio for Eclipse Experitest Digital Device Lab Experitest reporter * Any test framework, IDE and CI tools can be used

How the SeeTest platform support hands free continuous testing Epic Story thinning Prototype Acceptance Criteria Functional Spec Product Owner Analyst Product Owner Analyst Designer Analyst Tester

20 How the SeeTest platform support hands free continuous testing Epic Story thinning Prototype Acceptance Criteria Functional Spec Product Owner Analyst Product Owner Analyst Designer Analyst Tester Test Engineer Dev Engineer Dev-Test Feedback cycle 1 hour Showcase / Demo Sign-off Acceptance testing Automated testing Build & Deploy Code (incl. White box Test) Product Owner Tester Manual Testing Test Analytics Dev & Test Engineer Test development Grid Execution Test Analytics DevOps Engineer RESTful API to mass deploy application on targeted devices Grid Execution Test Analytics Dev & Test Eng. Dev & Debug Digital assurance Lab (SeeTestCloud) 20

21 01 Why do we need continuous testing? Agenda 02 The continuous testing environment 03 Step-by-step demo 04 Q&A 21

22 22 Thank You!

Turbo boost your digital app test automation with Jenkins

Turbo boost your digital app test automation with Jenkins Step-by-Step Tutorial May, 2018 Speakers Sheli Ashkenazi Sr. Product Manager Experitest Jonathan Aharon Sr. Sales Engineer Experitest 2 01 The