Static Testing on Life Cycle Of Testing Process
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
458
On Slideshare
457
From Embeds
1
Number of Embeds
1

Actions

Shares
Downloads
9
Comments
0
Likes
0

Embeds 1

http://www.linkedin.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Life  Cycle  of  Tes-ng  Process   “Sta-c  Tes-ng”   İbrahim ATAY | Consultant www.ibrahimatay.org | @ibrahim_atay
  • 2. Development  Process  Models   •  Sta5c  process  models   •  Waterfall  model   •  V-­‐Model     •  Incremental  process  models     •  Modern  approaches  (Agile)   •  extreme  Programing   •  Prototypic  development   •  Test-­‐driven  development    
  • 3. V-­‐Model   Use-­‐case  scenarios   Valida-on   Test  cases   Test  cases   Verifica-on   Test  cases   IABG  Informa,on  Technology  (V-­‐Model  Lifecycle  Process  Model)  
  • 4. Sta-c  Tes-ng   •  To  find  defects   •  Examine  the  work  product  for  errors   •  Without  execu-ng  the  code   Dynamic  Tes-ng   •  To  find  defects   •  use  the  work  product  to  collect  failures   •  Must  execute  the  code  
  • 5. Inspec-on  Process   Planning   •  •  •  •  •  Kick  Off   Prepara-on   Review   Mee-ng   Work  product  and  inspec-on  team  is  selected   Moderator(inspec-on  leader)  is  chosen   Define  entry  and  exit  criteria   Decide  which  path  of  work  product  to  review   Assign  the  roles  to  the  reviewers   Rework   Follow  up  
  • 6. Inspec-on  Process   Planning   Kick  Off   Prepara-on   Review   Mee-ng   •  Distribu-ng  documents   •  Explaining  the  objec-ves,  progress  and  documents   •  Checking  entry  criteria   Note:  role  assignments,  checking  rate,  the  pages  to  be  checked   Rework   Follow  up  
  • 7. Inspec-on  Process   Planning   Kick  Off   Prepara-on   Review   Mee-ng   Rework   •  The  par-cipants  work  individually  on  the  work  product  under  review   •  Can  use  the  related  documents,  rules  and  checklists  provided   •  Iden-fy  defects,  ques-ons  and  comments  and  write  a  report  for  them   Note:  should  use  checklist   Follow  up  
  • 8. Inspec-on  Process   Planning   Kick  Off   Prepara-on   Review   Mee-ng   Rework   Follow  up   •  The  mee-ng  typical  consists  of;  logging  discussion  and  decision  phase   •  The  mee-ng  is  moderated  by  moderator   •  During  the  logging  phase  the  issues  are  men-oned  page  by  page,  reviewer  by   reviewer,  and  should  not  discuss   •  In  discussion  phase,  focused  on  issues  and  classify  them(cri-cal,  major  or  minor)   •  At  the  end  of  mee-ng,  a  decision  on  the  work  product  under  review  has  to  be   made  by  the  par-cipants  
  • 9. Inspec-on  Process   Planning   Kick  Off   Prepara-on   Review   Mee-ng   Rework   Follow  up   •  Based  on  the  defects  detected,  the  author  will  improve  the  work  product  under   review  step  by  step   •  Changes  that  are  made  to  the  document  should  be  easy  to  iden-fy  during  follow   up  
  • 10. Inspec-on  Process   Planning   Kick  Off   Prepara-on   Review   Mee-ng   Rework   Follow  up   •  The  moderator  will  check  that  the  agreed  defects  have  been  addressed   •  Will  gather  metrics  such  as  how  -me  was  spent  on  the  review,  how  many   defects  were  found   •  Will  also  check  the  exit  criteria  to  ensure  that  they  have  been  met    
  • 11. V-­‐Model   Use-­‐case  scenarios   Valida-on   Test  cases   Test  cases   Verifica-on   Test  cases   IABG  Informa,on  Technology  (V-­‐Model  Lifecycle  Process  Model)  
  • 12. Technical  Review   •  İs  a  discussion  mee-ng  that  focuses  on  achieving  consensus  about  the   technical  content.       •  The  experts  that  are  needed  for  a  technical  review   •  Architects   •  Chief  designers   •  Key  users    
  • 13. Code  Review   A  code  review  is  a  special  kind  of  inspec,on  in  which  the  team  examine  a  code  and  fixes   any  defects  in  it.  
  • 14. Pair  Programming  
  • 15. Code  Review  Tools   hKp://en.wikipedia.org/wiki/List_of_tools_for_sta,c_code_analysis  
  • 16. Sta-c  Analysis  isn’t  Development  Tes-ng   hKp://agile.dzone.com/ar,cles/sta,c-­‐analysis-­‐isn%E2%80%99t  
  • 17. Thank  You.   İbrahim ATAY | Consultant www.ibrahimatay.org | @ibrahim_atay