|
1
|
- What do you bring to the table on an assignment?
- Presentation by Ronald Kohlman June 2010
|
|
2
|
- What is a Testing Framework?
- “Tools of the trade”; what are they?
- Test Phases, Test Stages, Testing Activities, Verification Methods, a
Testing Workflow, Status Reporting, Test Types
- Discussions:
- What do you bring to the table?
- What does the Client bring to the table?
- Why are you there?
- How do you adapt & why do you need to?
|
|
3
|
- This presentation is for you, as Testing Practice Leaders, with the aim
to generate healthy discussion and participation by you
- The ideas presented here are focussed on the high level attributes for a
testing framework
|
|
4
|
- This presentation is for you, as Testing Practice Leaders, with the aim
to generate healthy discussion and participation by you
- The ideas presented here are focussed on the high level attributes for a
testing framework
|
|
5
|
- It is not just a set of templates
- A process structure that encapsulates the testing activity
- A Methodology; that includes standards, policies, procedures and
techniques
- Contains management processes for managing the testing effort
- Requires:
- Consistency, Common approach, Adaptability, Depth & Variety of
Experience
|
|
6
|
- It is not just a set of templates
- A process structure that encapsulates the testing activity
- A Methodology; that includes standards, policies, procedures and
techniques
- Contains management processes for managing the testing effort
- Requires:
- Consistency, Common approach, Adaptability, Depth & Variety of
Experience
|
|
7
|
- Templates
- Strategy
- Master Test Plan
- Detailed Test Plan
- RTMs
- Others?
- Test Tools
- Estimation tools & Processes
|
|
8
|
- Templates
- Strategy
- Master Test Plan
- Detailed Test Plan
- RTMs
- Others?
- Test Tools
- Estimation tools & Processes
|
|
9
|
- Unit Test
- Systems Test
- Performance & Volume Test
- Systems Integration Test
- User Acceptance Test
- Pre-Production Test
|
|
10
|
- Unit Test
- Systems Test
- Performance & Volume Test
- Systems Integration Test
- User Acceptance Test
- Pre-Production Test
|
|
11
|
|
|
12
|
|
|
13
|
|
|
14
|
|
|
15
|
|
|
16
|
|
|
17
|
|
|
18
|
|
|
19
|
|
|
20
|
|
|
21
|
|
|
22
|
|
|
23
|
- All parts of the solution incorporate features or characteristics that
are not testable in a technical sense, but which must be verified using
an alternative method.
- The objectives of the Verification process include using established
criteria to conduct verification of the physical architecture (including
software and interfaces) from the lowest level up to the total system.
- There are 5 potential methods of verification that you can be engaged in
to verify the solution
- The most common verification method understood and used is “TEST”
|
|
24
|
- A typical workflow for testing activities and deliverables
- You may add or vary these basics
|
|
25
|
- Some generic metrics reporting requirements
- These vary depending upon the Testing Stage you are in for any
particular Test Phase
|
|
26
|
|
|
27
|
|
|
28
|
|
|
29
|
|
|
30
|
- What works for you?
- What doesn’t work you?
- What is the one thing that you would suggest as “a must have” in your
tool kit?
- Where do you go to source information to help you?
- Own knowledge base?
Colleagues?
Training?
Organisation?
- Internet? Books? Papers? Conferences?
- What knowledge do you pass on (what do you leave behind)?
- How do you approach the work?
|
|
31
|
- Their own processes, culture, ideas, practices and templates
- Their own problems, issues, and perceptions
- Organisation Maturity
- Ability to accept your inputs, or not
- Inability to clarify scope
- Inability to do it the “right way”
- Inability to understand testing (“Education”)
- Wanting to “cut corners” & squeeze time
|
|
32
|
- Their own processes, culture, ideas, practices and templates
- Their own problems, issues, and perceptions
- Organisation Maturity
- Ability to accept your inputs, or not
- Inability to clarify scope
- Inability to do it the “right way”
- Inability to understand testing (“Education”)
- Wanting to “cut corners” & squeeze time
|
|
33
|
- Their own processes, culture, ideas, practices and templates
- Their own problems, issues, and perceptions
- Organisation Maturity
- Ability to accept your inputs, or not
- Inability to clarify scope
- Inability to do it the “right way”
- Inability to understand testing (“Education”)
- Wanting to “cut corners” & squeeze time
|
|
34
|
- To assist the organisation in driving the delivery of their testing
requirements
- Help them to achieve their objectives
- Provide them with your testing practice experience and knowledge
- Provide guidance in the best approach for testing their “solution”
- Provide a “Framework” & Standardised approach
|
|
35
|
|
|
36
|
|