static testing on life cycle of testing process
Post on 20-May-2015
268 Views
Preview:
TRANSCRIPT
İbrahim ATAY | Consultant
www.ibrahimatay.org | @ibrahim_atay
Life Cycle of Tes-ng Process “Sta-c Tes-ng”
Development Process Models
• Modern approaches (Agile) • extreme Programing • Prototypic development • Test-‐driven development
• Sta5c process models • Waterfall model • V-‐Model
• Incremental process models
IABG Informa,on Technology (V-‐Model Lifecycle Process Model)
V-‐Model
Use-‐case scenarios
Test cases
Verifica-on
Valida-on
Test cases
Test cases
Sta-c Tes-ng Dynamic Tes-ng
• To find defects • Examine the work product for errors • Without execu-ng the code
• To find defects • use the work product to collect failures • Must execute the code
Planning Kick Off Prepara-on Review Mee-ng Rework Follow up
Inspec-on Process
• 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
Planning Kick Off Prepara-on Review Mee-ng Rework Follow up
Inspec-on Process
• Distribu-ng documents • Explaining the objec-ves, progress and documents • Checking entry criteria
Note: role assignments, checking rate, the pages to be checked
Planning Kick Off Prepara-on Review Mee-ng Rework Follow up
Inspec-on Process
• 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
Planning Kick Off Prepara-on Review Mee-ng Rework Follow up
Inspec-on Process
• 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
Planning Kick Off Prepara-on Review Mee-ng Rework Follow up
Inspec-on Process
• 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
Planning Kick Off Prepara-on Review Mee-ng Rework Follow up
Inspec-on Process
• 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
IABG Informa,on Technology (V-‐Model Lifecycle Process Model)
V-‐Model
Use-‐case scenarios
Test cases
Verifica-on
Valida-on
Test cases
Test cases
Technical Review
• The experts that are needed for a technical review
• Architects • Chief designers • Key users
• İs a discussion mee-ng that focuses on achieving consensus about the technical content.
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.
Pair Programming
Code Review Tools
hKp://en.wikipedia.org/wiki/List_of_tools_for_sta,c_code_analysis
Sta-c Analysis isn’t Development Tes-ng
hKp://agile.dzone.com/ar,cles/sta,c-‐analysis-‐isn%E2%80%99t
Thank You.
İbrahim ATAY | Consultant
www.ibrahimatay.org | @ibrahim_atay
top related