Integration Testing Approach BSA PL V2 Final

Embed Size (px)

Citation preview

  • 8/17/2019 Integration Testing Approach BSA PL V2 Final

    1/5

    ntegrated Unit Testing Engagement

    MetLife - Cognizant

  • 8/17/2019 Integration Testing Approach BSA PL V2 Final

    2/5

    © 2014 Cognizant

    Integrated Unit Testing – Where we t!

    Integrated Unit Testing"IUT# aims to im$%ement &'hift Left& Tstrateg( )( *om)ining +,a%it( ss,ran*e "+# and de.e%o$menof a software $ro/e*t ear%ier and more dee$%( in $ro/e*t $%an t

    e$anding the testing $rogram and red,*ing man$ower ae,i$ment needs

    e( 3erings

    5o*,s reas 6enets

    Analysis of Technical DesignSpecications Documents

    Code Review for StaticAnalysis

     Testing of Inter-ApplicationCoupling

    Eecute !igh priority"usiness Scenarios toarrest critical defects#"etter test coverage thantraditional $A Testing

     Customer %alue Adds

    &inimum Defectwith maimum tcoverage!igh release pre

    Reduction in test) cost in su(se*testing cycles

    $$%i*ation 7e.e%o$ment8Enhan*ement

    IUT +,a%it( ss,ran*

  • 8/17/2019 Integration Testing Approach BSA PL V2 Final

    3/5

    © 2014 Cognizant

    IUT $$roa*h

     Analysis

    • BRD/FRD Analysis• Technical Spec Doc• Static Code Analysis

    Design Execution

    Am(iguity trac'er

     Test +lan Document Test ScenarioDocumentAutomation Script

     Test ,ogther (servations

    • Test planning• Design high priority

    scenarios•  Automation Script

    design

    • Execute Automationscripts

    • Validate Integration points

    • Deect Reportingand interacting !ith AD Team or Bug "x 

    • Deect Retesting

         P    r    o     j    e    c     t    s

    • :ew ;rod,*tLa,n*hes

    • Ma/or andMinorenhan*ements

    • $$%i*ation

  • 8/17/2019 Integration Testing Approach BSA PL V2 Final

    4/5

    © 2014 Cognizant

  • 8/17/2019 Integration Testing Approach BSA PL V2 Final

    5/5© 2014 Cognizant

     Test Automation in I>T

       Excel Comparator A useful solution to compare similar datasets?etracts eported in ecel formats in order to detect discrepancies#

    !"#  timelines are limite$ an$ s%ort !hen compared to traditional#A timelines$ The o%erall moti%e is to $etect t%e maximum num&erof $efects &eore the #A testing &egins$ Considering the limited time'span or I(T and its o&)ecti%es the pro)ect team need to &an* on theollo!ing +

    ,$ (se o s*illed resources !ho has good &usiness or application*no!ledge + !ho can ho%er around the deect prone areas oapplication and expose deects

    '( !ncrease$ test coverage

    #%e secon$ point imply extensive use of automation tools an$solution accelerators t%at )oul$ potentially improve team

     pro$uctivity 

    Business rules ta&les va

      Data set vali$

    *e) Busine

    Do)nstream E

    Correspon$ence PD ,ali

    #ools an$ Solution Accelerators t%at can &eleverage$ -

     Cogni.ant proprietary tool for PD ,ali$ation PD Automation PR/ +D@ Automation +ro is an E5E +D@ validation solution that greatly reduces the manual e=ort re*uired for +D@ document valid

    comprehensive features that addresses the 'ey dimensions of +D@ validation vi#6 comparison6 etraction and validation

     !n%ouse #est Automation rame)or0Agnostic hy(rid automation framewor' that com(ines the (est practices of 'eyword driven and data driven approaches#

     

     BR# ,ali$ation Macro

     This is an ecel (ased macro that ta'es two versions of (usiness rules?admin ta(les as input B say one (efore code drop anand highlights the di=erences (etween the two versions# The output result is then veried manually - Epected mismatcheam(iguities are reported#