Continuous Integration April 2014 tap|QA Presentation.

Continuous Integration

April 2014

tap|QA Presentation

2

Welcome tap|QA OverviewRick Faulise Introduction

AgendaOverviewWhat is involved?MobileSkill Sets

Solutions Focus Pays

Copyright © 2014 TAP/QA, LLC – Confidential & Proprietary. For more information: www.tapQA.com


3


Success StoriesOur Mission


tap|OVERVIEW

Focus Pays

Client Examples

Our mission is to provide our clients with focused solutions for delivering Strategic and Tactical Quality Initiatives

We pride ourselves on hiring highly talented people that deliver high quality work for our Clients

Why tap|QA?

Our investment in our employees has allowed us to meet the growing demand or QA roles. Including the new Technologies and Business Requirements every QA now has along with the desire and drive in Quality.

Our innovation has created new approaches in competing with Off-shore models with our tap|Lakeshore. Our tap|Technology team is advancing leading edge ideas in Continuous Integration, Delivery and Deployment.

4



Rick Faulise

Experience Over 15 years of QA experienceCertifications:

BA (B2T, IIBA)Automation Mercury Suite (HP)

Development BackgroundC, C#, C++JavaHTMLXMLOthers

5

Continuous Integration – The practice of everyone involved with code, merging their local copies multiple times a day.

Attempting to prevent Deployment Delays




6

Continuous Delivery – The automated process of implementing, validating and reporting code from development to production. But only moving into Production after passing a manual quality gate.

Continuous Deployment – The automated process of implementing, validating and reporting code from development to production.



Delivery Vs. Deployment

7



Continuous Integration Cont.

8



Traditional Vs. CI Automation

UI Automation:QTPSelenuim

Load Testing:LoadRunnerJmeter

UI Automation:QTPSelenuim

Load Testing:LoadrunnerJmeter

Expanded Harness:JmeterCodedUI

Test Harness:JunitSoapUI

9

Local Developer Level:Unit tests (TDD)Execute in < 30 seconds



What is Involved ?

10

QA Takes ownership of Test Harness:Enhance and Expand Test Harness

Adding CodeAdditional Test Scenarios



Where QA is Involved ?

11

CI Implementation at Development Master:Unit, Smoke, and Core Functionality tests

Adding CodeAdditional Test Scenarios

Jmeter, SoapUI, Visual Studio, TFS, etc.Execute in < 2 minutes



Where QA is Involved Cont.

12



Deployment Management

13

QA LevelSmoke, Expanded Core Functionality, and UI testsQTP, Selenium, Jmeter, SoapUI, TFS, etc.Execute in < 2 – 4 hours




14




Stage LevelSmoke, Complete Core functionality, Full UI, and Load testsLoadRunner, Jmeter, LoadUI, etc.Execute in < 6 – 12 hours

15



Mobile

MobileReplicate all harnesses across all supported platforms

Windows 8 (C#) Android (Java)IOS (objectiveC)

16

Technical skills:Architect level – Work with systems architect designing

CI automated processes, and implement of initial automation framework POC.

Automation Engineer – Expansion of automation coverage and maintenance of framework.

Non-Technical:QA Analyst– Requirement decomposition, writing of

test scenarios, reviewing of failed executions.



Skill Sets

17

Trend:Current Requirements – Since CI is heavily integrated

within technology the teams are attempted to be built with QA Analysts that have Architect and Automation Skills.



Observations

Architect

Automation AnalystQA Analyst

Questions?


Continuous Integration April 2014 tap|QA Presentation.

Documents

Transcript of Continuous Integration April 2014 tap|QA Presentation.