Fundamental Test Process New
Upcoming SlideShare
Loading in...5
×
 

Fundamental Test Process New

on

  • 146 views

 

Statistics

Views

Total Views
146
Slideshare-icon Views on SlideShare
144
Embed Views
2

Actions

Likes
0
Downloads
5
Comments
0

1 Embed 2

http://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Fundamental Test Process New Fundamental Test Process New Presentation Transcript

    • Software Testing Foundations #1.1 The Fundamental Testing Process Nikita Knysh nknysh@gmail.com http://www.facebook.com/groups/istqb/
    • The Fundamental Testing Process Begin Planning and Analysis and Design Implementation and Execution Evaluation of Test Exit Criteria Post Testing Activities End Control
    • Planning and Control • Planning: ▫ Test policy, Test strategy ▫ Test plan (test resources, test intensity for system parts and characteristics, priorities of test, tool support). • Control: compare actual situation with plan and adjust the plan. Complete testing is not possible. Faults can cause high costs. Balance is to be kept by Test Manager.
    • Analysis & Design • Creating logical test cases (positive and negative) based on test basis. • Test case explosion
    • Implementation & Execution • Creating concrete (and easily reproducible!) test cases out of logical ones, preparing test harness (harnesses, drivers, simulators, etc.) • Check test environment, execute test cases according to priorities defined when planning • Log results, and describe failures in reproducible way. • The pesticide paradox
    • Evaluation of Test Exit Criteria, Reporting • All exit criteria should be met to stop testing. So several (!) test cycles should be planned. • Criteria: defect detection percentage (DDP) and defect importance; in practice: time & cost. • Write test summary report for stakeholders.
    • Post Testing Activities (Test Closure) • Experiences from testing work should be analyzed and made available for further projects. ▫ ▫ ▫ ▫ ▫ Planned vs achieved results Analysis of unexpected events happened Analysis of defects Change requests: Still Open? Why not implemented? How good was user acceptance before deploy?