The document discusses promoting technical QA from good to great by shifting from a defect fighter to solution provider role. It outlines expanding QA skillsets to include domain expertise, testing innovation, automation, and product knowledge. QA's can explore skills like root cause analysis, performance testing, defect prevention, networking and architecture knowledge, testing process activities, and testing skills in areas like reliability, coverage, and quality risk analysis. The goal is for QA's to become technical influencers and take initiative in proposing solutions rather than just finding and reporting defects.

1. ROLE OF TECHNICAL QA - FROM GOOD
TO GREAT
Initial updated by Tony_HsuClassificationPresenter Name
Presenter Title

2.  Mission Statement
 Domain toward Solution Provider
 QA Skill set to explore
 Discussion Summary within QMs
 Q&A through sharing
 Reference
Classification
Agenda

3. Mission Statement
Promote the value of Technical QA
from Good to Great. (Defect Fighter to Solution Provider)
Classification
Mission Statement

4. Defect Fighters Solution Provider
QAs QA
Reviewer, Follower by design Technical Influence & initiative
Classification
Technical influence
Solution Provider
QA
Defect Fighters -- QAs

5. DOMAIN TOWARD SOLUTION PROVIDER
Classification
Details
Root/Cause
Analysis with
solution
proposal
Testing
“Automation”
Leverage
existing Tools
Innovation on
solution delivery
and testing
approach
i.e. Performance
Testing.
New area
Defect
prevention
Best Defect Fighter, Reviewer, Testing case execution,
(Soft-skill) Written/Oral communication
Solution Provider
Domain Expert
with use case
initiative
proposal.
i.e. 1. Threat, 2.
Customer
Insihgt
Networking,
Linux, AD,
Architecture and
design flow of
platform
Ownership/Conv
erage of the
whole
module/solution
/product/seg/Tr
endmicro.

6. ACTIVITIES OF IN EACH TESTING PROCESS
 Organizing for testing
 Define test scope.
 Organize the test team.
 Assess development plan and status.
 Developing the test plan
 Perform risk analysis
 Write the test plan.
 Verification testing
 Test software requirements
 Test software design
 Test software construction
 Validation testing
 Perform validation testing
 Record test results
• Analyzing and reporting test results
– Analyze the test results
– Develop test reports
• Acceptance and operational testing
– Perform acceptance testing
– Test software installation
– Test software changes
• Post-implementation analysis

7. Approach to Innovation Innovative Testing approach.
Innovation on product/solution.
Automation Uses of Tool or testing automation for
efficiency/effectiveness.
Configuration Test Data generator
Version control
Integration testing
Configuration Management
Execution Manual Scripted
Manual Exploratory
Automated
Bug Isolation
Bug Reporting
Testing status reporting
Technical Domain Knowledge Antivirus domain knowledge
Programming: C, Shell Script, Automation
Operation System: Windows, Linux
Networking: Network Appliance, VPN/firewall, AD
environment, Proxy
System/Server: Database Server
Application: Virtualization, Browser
Classification
Opportunity for QA Skillset to Explore - 2

8. Product Knowledge L2 with L3 specific feature
L3 with specific product
L3 with product and integration module
L4 understanding of the whole project/solution.
General Qualifications Oral communication
Written formal/informal communication
Cross-function relationship building
Business/Technical Trends
Continuing Education
Cross-training
Testing Skills – General Testing standard
Testing/development process maturity
Change Management
I18n testing methodology
Testing Planning Estimation
Documentation
Cost of Quality
Quality Risk/Failure mode and Effects Analysis
Testing Design& Development Behavioral (Black-box), Structural (White-box)
Static (Requirements, spec, documentation)
Reliability (Statistics)
Performance (Modeling/Simulation/Testing)
Code/Dataflow CoverageClassification
Opportunity for QA Skillset to Explore - 1