QA Team Goes to Agile and Continuous integration

QA Team Goes to Agile and Continuous integration

• 1.
  1 Attendees
• 2.
  SCQAA “CHANGE IS CONSTANT” JenniferWong 2 If you are interested to be notified for our next meeting, please send an email to Sujit at sujit.ghosh@3sgbs.com QA Team Goes to Agile and Continuous integration
• 3.
  Methodologies – whythe change? 3
• 4.
  What is Agile? 4
• 5.
  What are thevalues? 5Source: www.agilemanifesto.org
• 6.
  Agile Team Structure 6
• 7.
  QA and TestSuccess Factors • Planning & Strategy • Data Management • Asset Management • Automation • Metrics • Skills 7
• 8.
  Eliminate Developer andTester Friction with Full virtual test data sharing • Testers continue testing while developers fix the bug. • Developers can quickly fix bugs in a previous release and resume new development work • Analysts can also quickly perform detailed data analysis with no Production system impact or access Solving the Test Data challenge 8 Tester resets in minutes, continues testing Tester logs defect and creates a bookmark of the same name and shares with development Tester encounters error 1:30:56 P.M. Developer Errors are found earlier using real business data Developer opens defect ticket and creates a branch off of the bookmark in minutes After fixing the defect, the developer activates the branch he was previously working on and continues development Developer / QA / Analyst
• 9.
  Data for TestParallelism 9 AUG 1, 11:50:33 AUG 5, 7:28:29 AUG 6, 3:17:51 Application A Application B Application C • Maximize test time and improve data quality • Decouple reliance on multiple Silo’ed application teams • Easily sync point-in-time data for all applications from a single point of control • Reset in minutes, data guaranteed in sync >> higher quality testing, less rework • Self-service resets replace long refresh processes >> new resources available for other projects
• 10.
  Test Asset Management– when your IP matters! 10
• 11.
  Test Automation integration 11
• 12.
  Test Automation: Speed,Quality and Cost Solutions 12 BPT Action/Component Hybrid BDD
• 13.
  Automation Frameworks 13 Change itto % coverage Framework Description Pros Cons BPT Framework (HP) • First Framework from HP used for Automating QNXT Scripts • Converted from BPT to Hybrid in 2011-12 Provided by HP • Slow • Integration Issues with QC 10 • Cost Involved in using the Framework Hybrid Framework • Combination of Data Driven & Keyword driven • Structured framework with defined place for all resources (OR, Env Files, Functional Lib, Initialization Settings etc. • Modular (Use of Functions) • Data Parametrization (incl. queries) • Ease to Script using excel sheet • Reusability • Parallel execution not possible. • Excel sheets may get corrupted or locked (Resources outside ALM) • More maintenance required. Action/Component based Framework • Enhanced Hybrid Framework with Modules divided into Components/ Actions (Example – Login screen) • All Resources within ALM • Integration with Mobile Labs • Easy of use from ALM (Doesn’t require automation knowledge to execute) • Parallel execution possible • Ease of maintenance • All resources centralized in ALM • All results in ALM for analysis • Initial time to design components scripts may take time, but eventually it will be more advantage for additional test cases. BDD Framework • Supports DevOps and In Sprint automation • Built using Open Source automation tools • Improved Time to Market • No licensing cost except Visual Studio for C# • Need a stable DevOps kind of environment to start with
• 14.
  1 4 Selenium Test AutomationFramework AUT Test Case Test Case Test Step Test Step Test Step Test Step Test Step Action Action Action Action Action Reusable methods broken down to granular functional operations • Reusable components at framework level are available across applications (AUTs) • Test Cases written for one environment e.g. DEV can be run in other environment with simple changes to the configuration File • Actions / methods once created become reusable as all environment specific data is passed from configuration file • Configurable Input data & Expected results for each Actions and are passed at run time • New Test Cases for SIT , E2E and UAT can be created by calling reusable methods directly • Reusability is at both Test Case & Action levels Framework components – Database C# Code Reusable Components Framework Level
• 15.
  Fundamentals Deliver Value! • TimeTo Market • Low Cost Solutions • High Quality Product 15