Your SlideShare is downloading. ×
Software Testing Foundations Part 1 - Basics Continued - Fundamental Testing Process
Software Testing Foundations Part 1 - Basics Continued - Fundamental Testing Process
Software Testing Foundations Part 1 - Basics Continued - Fundamental Testing Process
Software Testing Foundations Part 1 - Basics Continued - Fundamental Testing Process
Software Testing Foundations Part 1 - Basics Continued - Fundamental Testing Process
Software Testing Foundations Part 1 - Basics Continued - Fundamental Testing Process
Software Testing Foundations Part 1 - Basics Continued - Fundamental Testing Process
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Software Testing Foundations Part 1 - Basics Continued - Fundamental Testing Process

314

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
314
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

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. Software Testing Foundations #1.1The Fundamental Testing ProcessNikita Knyshnknysh@gmail.comhttp://www.facebook.com/groups/istqb/
  • 2. The Fundamental Testing Process Begin Planning and Control Analysis and Design Implementation and Execution Evaluation of Test Exit Criteria Post Testing Activities End
  • 3. Planning and Control• Planning: ▫ 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 highcosts. Balance is to be kept by Test Manager.
  • 4. Analysis & Design• Creating logical test cases (positive and negative) based on test basis.• Test case explosion
  • 5. 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
  • 6. 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.
  • 7. Post Testing Activities (Test Closure)• Experiences from testing work should be analyzed and made available for further projects.

×