Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Lesson 4

Test Estimates, Planning, Metrics
by

Artem Vasiuk

on 9 January 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Lesson 4

Test Plan = Test Suite
TesterBootCamp
Lesson 1
Each project is started from....
Test Plan
...is a management document that shows
How the testing will be done
Who will do it
What will be tested
What the test coverage will be
How long it will take
Introduction
Test Items
Features TO BE and NOT TO BE tested
Testing Types to be applied
Test Deliverables
Team and Responsibilities
Estimates and Schedule
Entry and Exit criteria
Includes following basic sections:
Test Metrics
"We cannot control what we cannot measure"

"We cannot improve what we cannot control"

Executed/Not tested
Passed/Failed
First run failure
Re-Execution


Reported/Fixed
Applied/Rejected
Common metrics
Calculated metrics
% Defects reported & corrected
% Test coverage
% Test cases passed
% Test cases efficiency
% Defects slipped
Failed test cases
100%
Executed test cases
24
---- x 100% = 20%
117
Production defects
Reported defects*
* related and correct issues
100%
2
---- x 100% = 2 %
95
37
---- x 100% = 148 %
25
OK
(98% efficient)
FAIL
(0% efficient + 48% worse)
Passed TC
Sprint
start
end
Test Estimation
Estimation is the process of finding an estimate of a result which is usable even if input data may be incomplete or uncertain.
Example:
8 hour work day
Coffee
15 min per 1 test case


Run 23 Test cases
Prepare Report - 1 h

Given
Count
8h - 1h = 7 hrs
7h - .50' = 6h 10'
.15' x 23 = 5h 45'

Task
25 mins
Estimation Techniques
Factors:
Size of a system
Types of testing required
Scripted or Exploratory test
'Non testing' activities
Test phases
Approaches:
1. Company method/model
2. Experience from other projects
3. Expert's help
4. Your own judgement
5. Software size based
6. Activities based
Important!
Check your expectations with reality
and adjust accordingly.
>Deming Cycle
Factors & Approaches
Profit:
(5 times x 10 mins)
TC
BUT!
- Test cases blocked by defects
- Defects require management
- Version (build) management
- Technical and Social risks
Estimates are dependent
Based on Test Cases:
Based on Defects:
PLANNING
>
>
>
>
>
Test Plan types:
- Master Test Plan
- Iteration Test Plan
Report
Custom metrics?
Thank you!
artem.vasiuk@gmail.com
arty.vasyuk
Email:
Skype:
What is SDLC
Testing goals on each stage
Skills expected from Tester
Profit from Tester
Testing types
The right one, The right time
Differences in platforms
Type per phase of a SDLC
Lesson 2
*past
*past
No requirements reality
Test Techniques
Survival plan
Acting responsible
Lesson 3
*past
Test Plan
Estimates
Metrics
Lesson 4
Full transcript