Scrum_BLR 11th meet up 13 dec-2014 - SDET - They Way to go for Testers - Jaya Prakash
-
Upload
scrumblr -
Category
Technology
-
view
386 -
download
1
Transcript of Scrum_BLR 11th meet up 13 dec-2014 - SDET - They Way to go for Testers - Jaya Prakash
Lets go back ….
1-3
• Engineering = Development (only)
• Testing = See if it works
• Very ‘traditional’… very ‘waterfall’…
• Basic Software quality issues
• To fix these issues, Testers were hired.
1-3
Is that the future of software testers?No, its changing…. So what should testers do?Go beyond Test Defects…
Why go beyond Test Defects?
1-3
Defect Removal Method Minimum Efficiency Maximum Efficiency Average Efficiency
Formal design inspection 65% 97% 87%
Formal code inspection 60% 96% 85%
Static analysis 65% 95% 85%
Pair Programming 40% 65% 55%
Informal Peer Review 35% 60% 50%
Risk-based Testing 55% 80% 70%
System Testing 27% 55% 42%
Unit Testing 20% 50% 40%
Regression Testing 35% 45% 35%
Acceptance Testing 15% 40% 35%
Source: The Economics of Software Quality by “Capers Jones” & “Olivier Bonsignour”
Cross-functionality Skilled… !
1-3
Tester’s Skill Boundary…
Test Design
Test Planning
ExploratoryUsability
Test Case Preparation
Performance TestingSoak Testing
ReliabilityAd-hoc
The ‘T’ Skill
1-3
Functional Testing
Exploratory Testing
Performance Testing
Security Testing
UI Testing Ad-hoc Testing
4 Quadrants of Agile Testing
December 24, 2014
12
Without Q1, Q2-Q4
will be harder
Do As Early As
Possible
Right Product
Product Right
Build these skills
Tester’s Skill Boundary…
Test Design
Test Planning
ExploratoryUsability
Test Case Preparation
Performance TestingSoak Testing
ReliabilityAd-hoc
Tester’s Skill Boundary - PROGRAMMING
Test Design
Test Planning
ExploratoryUsability
Test Case Preparation
Performance TestingSoak Testing
ReliabilityAd-hoc
The ‘T’ Skill
1-3
Functional Testing
Exploratory Testing
Performance Testing
Security Testing
UI Testing Ad-hoc Testing
Helps in understanding ‘HOW’ instead of just ‘WHAT’Contribute to the team wherever required
Design/Code Review
Defect Causal Analysis
Programming
Automation
Tools Development
Tools Knowledge (CI)
Static Analysis
PROGRAMMING – Tester’s Contribution
• Code Peer Review
• Design Peer Review
• DB Design Review
• Code coverage measurement
• Code coverage increase
• Identification of dead code
• Automation scope identification based on UT CC
• Defect Causal Analysis
• Defect Fixing
• Tools Development
Tester’s Skill Boundary - AUTOMATION
Test Design
Test Planning
ExploratoryUsability
Test Case Preparation
Performance TestingSoak Testing
ReliabilityAd-hoc
December 24, 2014
18
Effort
High
Moderate
Low
Execution Time
High
Moderate
Low
ROI
Low
Moderate
High
Feedback
Late
Moderate
Early
Mike Cohn’s Agile Automation Pyramid
Tester’s Skill Boundary - AUTOMATION
Test Design
Test Planning
ExploratoryUsability
Test Case Preparation
Performance TestingSoak Testing
ReliabilityAd-hoc
Developer Develops, Tester Tests !
Developer Tester
Responsible for testing own code Understand the quality of code
Primarily responsible for dev process (design,
code, unit test etc)
Be part of all reviews. Understand dev
process.
Understand the testing process. Contribute to
testing as required
Primarily responsible for testing
Daily develop, build, test code Daily test the product
Responsible for unit automation. Contribute to
others as required
Responsible for functional, regression
automation. Help in UT if requiredDeveloper still develops, tester still tests !
Why SDETs?
High Code Coverage
Increased Early Defect Detection
Reduced Test Cycle Time
Increased SDET Staff
SDET Career Path
Grade Software Developer Software Tester SDET
13 Dir.Software Engineering / Sr. Solutions Architect
Dir of Quality / Sr. Solutions Architect
Sr. SDET Solutions Architect
12 Senior Engineering Manager / Solutions Architect
Senior Engineering Manager / Solutions Architect
SDET Solutions Architect
11 Senior Manager / Software Architect
Senior Manager / Software Test Architect
SDET Architect
10 Dev Manager / Tech Specialist QA Manager / QA Tech Specialist
SDET Specialist
9 Senior Software Dev Lead Senior Software QA Lead Senior Principal SDET
8 Software Dev Lead Software QA Lead Principal SDET
7 Senior Dev Engineer Senior QA Engineer Senior SDET
6 Software Dev Engineer Software QA Engineer SDET
5 Associate Dev Engineer Associate QA Engineer Associate SDET
DEFINE SDET CAREER !
How do we build SDET Skills / Competencies?
Test Planning
Domain SkillsProgramming
Automation
White box
SDET Conversion
December 24, 2014
27
Technical SkillsNeeds
ImprovementCompetent Exceptional – A Role Model
Test Planning X
Programming X
Domain/System Knowledge X
Automation X
White Box Testing X
Dev Manager QA Manager BU Quality Leader HRSDET Panel
AGILE & SDET
• At least 1 SDET (identified) individual per scrum team
• Every sprint, at least one cross-functional skill to be executed by SDETs
• Tracked as part of DOD
• Provide Effort, Time, Support to SDET to build skills
• Track SDET competencies on a monthly basis
Success Stories…
Fixed 70+ Memory LeaksDeveloped 12000+ LOC10000+ lines of UT code
Achieved 65% UT code coverageMentors aspiring SDET engineers
Built multiple utility tools40% code review defects foundCreated Regression suite for the portfolio