The document presents a workshop led by Jim Trentadue on managing software testing by focusing on dependencies rather than activities. It details the complexities of testing processes, including the roles of project managers, business analysts, and developers in test case and defect management, as well as highlights the importance of collaboration and communication in agile testing environments. Key takeaways emphasize the need to understand traditional test deliverables and to analyze the impact of various entities on the testing process.

1.
T19
Test
Management
10/5/17
15:00
Manage
Testing
by
Dependencies-­‐Not
Activities
Presented
by:
Jim
Trentadue
Independent
Consultant
Brought
to
you
by:
350
Corporate
Way,
Suite
400,
Orange
Park,
FL
32073
888-­‐-­‐-­‐268-­‐-­‐-­‐8770
·∙·∙
904-­‐-­‐-­‐278-­‐-­‐-­‐0524
-­‐
info@techwell.com
-­‐
http://www.starwest.techwell.com/

2.
Jim
Trentadue
Independent
Consultant
Jim
Trentadue
has
more
than
seventeen
years
of
experience
as
a
coordinator
and
manager
in
the
software
testing
field.
In
his
various
career
roles
in
testing,
Jim
has
focused
on
test
execution,
automation,
management,
environment
management,
standards
deployment,
and
test
tool
implementation.
In
the
area
of
offshore
testing,
Jim
has
worked
with
multiple
large
firms
to
develop
and
coordinate
cohesive
relationships.
As
a
guest
speaker
at
the
University
of
South
Florida’s
software
testing
class,
Jim
mentors
students
on
the
testing
industry
and
trends
for
establishing
future
job
searches
and
continued
training.Currently,
Jim
has
started
his
own
Test
Automation
Foundations
&
Principles
workshop
aimed
at
helping
manual
testers
get
started
with
automation.

3. 1
Test
Management
by
Dependencies
Jim
Trentadue
So0ware
Quality
&
Innova8on
Leader
Jim.Trentadue@outlook.com
Agenda
2
Unresolved
Tes8ng
Tasks
3
Breakdown
of
Test
Ac8vi8es:
Dependencies
&
Rela8onships
4
5
Session
Recap
Impact
Analysis
Test
Management
by
Outsiders
1

4. 2
Test Management by Outsiders
What testing artifacts do non-testing consumers care about?
Test Execution
Test
Documentation
Test Planning
Test Cases
Test Cases
Created
Test Cases
Executed
Test Cases Re-
Executed
Defects
Created
Defects
Tested /
Retested
Test Ar4facts

5. 3
What about Test Cases & Defects?
PM
TC Assigned To in
Project Schedule /
Sprint Iteration
BA
TC Traced to
Requirements /
User Stories
DEV
TC Navigated
properly
Upper Mgmt
TC Contributions
by person
TEST
CASES
PM
Defects Colliding
with release date
BA
Defects Validity
against specs
DEV
Defects Impact
against modules
Upper Mgmt
Defect Churn
against each build
DEFECTS
Standard Views
SQA Managers, Coordinators or Leads, are responsible for
Create Test
Scenarios
Create Test
Cases
Open
Defects
Report and
Repeat
Manual Testing Process Test Automation Planning
Automation
Workload How many planned existing
automated TC’s will be run
How many script modifications
in current library are required
How many TC’s will be created
fresh for release
Test Approach before Test Cases

6. 4
Unresolved Tes4ng Tasks
Questions arise, who is…
Environment?
• Preparing the
environment(s)
• Coordinating the
refresh activities
• Else is working in
same region
Testing Type?
• Creating scenarios
for integration test
• Writing / Executing
integration artifacts
• Reporting the test
status regularly
UAT?
• Guiding execution
in AQM system
• Organizing their
data and area
• Managing the
defect process
Manual Tes4ng

7. 5
Questions arise, who is…
Data?
• Ensuring data is
automation ready
• Mapping data to
respective tests
• Preparing data
before test runs
Modules?
• Reviewing impact
of reqs / stories
• Reviewing the
functional tests
• Aligning with Dev
& QA for changes
Environment?
• Running sanity run
for current tests
• Building test suite
of automated tests
• Coordinating with
Dev & QA on UI
Test Automa4on
Besides Testing the Story, what are testers doing?
• Work on
Auto / CI
Test Plan
• Demo the
solution
for team
• Accept /
reject
story
• Peer or
code with
PO / DEV
Reviewing Validating
BuildingProving
How do all of these
testing tasks relate
to the primary test
deliverable?
Life of an Agile (ish) Tester

8. 6
Introduc4on to Test Ac4vi4es
Breaking down the relationships
Project
Deliverable
Test
Cases
Written
Test
Cases
Executed
Defects
Reported
Dependencies & Rela4onships

9. 7
◌ Personnel allocation
◌ Environment(s)
◌ Data Management
◌ Tools Administration
Test Strategy
Completed
◌ Testing Types Defined
◌ Manual vs. Automated
◌ Automation Alignment
◌ Integration Coordination
Test Scenarios
Reviewed
◌ Peer Review
◌ Test Schedule
◌ Test Suite Build-Out
◌ Validation Defined
Test Cases
Written
Plan
Coordinate
Manage
Document
Test Case Prepara4on
◌ Code Deployment
◌ Environment(s)
◌ UAT Synchronization
◌ Build Smoke Test
New
Build
Delivered
◌ Automated Tests
◌ Manual Readiness
◌ SQA Retest Verification
◌ UAT Retest Verification
Test
ExecuCon
Commenced
◌ AQM Coordination
◌ Capture Team Results
◌ Progress Measured
◌ Retrospective Input
Test
Results
Reported
Coordinate
Execute
Document
Manage
Test Case Execu4on

10. 8
◌ Build Package
◌ Module Review
◌ Environment(s)
◌ Assign Personnel
Defects
Deployed
◌ UAT Coordination
◌ Defect Review
◌ Rerun Sanity Test
◌ Capture Team Results
Defects
/
TC’s
Retested
◌ TC / Defect complete
◌ Release complete
◌ Test Summary write-up
◌ Coordinate Go – No Go
Defects
/
TC’s
Signed
Off
Manage
Execute
Coordinate
Document
Defect Management
Test Case Preparation
Personnel allocation
Environment(s)
Data Management
Testing Types Defined
Manual vs. Automated
Validation Defined
Test Suite Build-Out
Test Schedule
Test Case Execution Defect Management
Plan Ac4vity

11. 9
Test Case Preparation
Automation Alignment
Integration Coordination
Test Case Execution
UAT Synchronization
AQM Coordination
Environment(s)
Defect Management
Module Review
Environment(s)
Assign Personnel
UAT Coordination
Coordinate Go-No Go
Coordinate Ac4vity
Test Case Preparation
Automation Alignment
Integration Coordination
Test Case Execution
UAT Synchronization
AQM Coordination
Environment(s)
Defect Management
Module Review
Environment(s)
Assign Personnel
UAT Coordination
Coordinate Go-No Go
Manage Ac4vity

12. 10
Test Case Preparation
Personnel allocation
Environment(s)
Data Management
Testing Types Defined
Manual vs. Automated
Validation Defined
Test Suite Build-Out
Test Schedule
Test Case Execution
Progress Measured
Retrospective Input
Defect Management
Test Summary write-up
Document Ac4vity
Test Case Preparation Test Case Execution
Build Smoke Test
Automated Tests
Manual Readiness
SQA Retest Verification
UAT Retest Verification
Defect Management
Rerun Sanity Test
Execute Ac4vity

13. 11
Impact Analysis
Let’s examine different roles in QA
QA
Team
Functional /
Automation
Tester
Test
Specialist
Environment,
Coordination,
Data Tool
Specialist
Automation,
Web Services,
AQM
Personnel Impact

14. 12
How can these tasks impact the tests?
Data
Mgmt
56 TC’s
28 System
9 Automated
8 Integration
11 UAT
AQM
Admin
120 TC’s
84 System
9 Automated
9 Integration
18 UAT
Test Impact
Session Recap

15. 13
Key takeaways for Test Management by Entities
q Traditional test deliverables are the baseline for test assessment
q Be sure to answer questions to all supporting work
q Drill-down from your process and extract common themes
q Build the activity by associated common tasks
q Illustrate the impact of that entity to the traditional test deliverable
Presenta4on Recap
Thank
you
for
aMending!
Jim
Trentadue
So0ware
Quality
&
Innova8on
Leader
Jim.Trentadue@outlook.com