Joy Shafer October, 2011 - PowerPoint PPT Presentation

Joy Shafer October, 2011 ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 1

Introduction  Why am I here?  Why are you here? ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 2

Sabotaging Quality Sacrificing long-term for short term  Investment in test, particularly test  Investment in test, particularly test automation automation  Software quality  Software quality  Ability to maintain software or service  Ability to maintain software or service  Investment in infrastructure  Investment in infrastructure  Employee morale and vitality  Employee morale and vitality Most of the time, no one sets out to sabotage quality, things just get away from them. ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 3

Investment in Test  Automated BVTs  Automated BVTs  Continuous Integration  Continuous Integration  Unit testing  Unit testing  Automated regression tests  Automated regression tests  The ability to emulate external components  The ability to emulate external components ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 4

Automated BVTs  Robust (reliably functional)  Robust (reliably functional)  Not dependent on other systems or services  Not dependent on other systems or services  Definitive  Definitive  If it fails it’s because of a code issue not a timing  If it fails it’s because of a code issue not a timing issue, data issue, setup issue, etc. issue, data issue, setup issue, etc.  Start with basic tests and add on  Start with basic tests and add on ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 5

Continuous Integration A cornerstone of efficient software development  Daily integration  Daily integration  Scheduled BVTs & Automated Regression tests  Scheduled BVTs & Automated Regression tests Adequate test automation is required ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 6

Unit Testing  Cleaner code  Cleaner code  Better designed code  Better designed code  Tools  Tools  Test hooks  Test hooks  Mock objects  Mock objects  Better appreciation by developers of the  Better appreciation by developers of the challenges testers face challenges testers face Management support is required ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 7

Automated Regression Tests Without automated regression testing, teams Without automated regression testing, teams of manual testers will need to comb through of manual testers will need to comb through the software with every release, laboriously the software with every release, laboriously running the same tests they’ve run countless running the same tests they’ve run countless times before. times before. ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 8

The ability to emulate external components  Don’t get too complicated  Don’t get too complicated  Check with other teams for emulators you  Check with other teams for emulators you can modify can modify  Keep up-to-date  Keep up-to-date  Extremely useful, maybe essential, for  Extremely useful, maybe essential, for performance testing performance testing Invest early, invest often ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 9

Software Quality  Fix bugs as you find them  Fix bugs as you find them  Less time overall on bug fixes  Less time overall on bug fixes  Ship cycles will be shorter and more predictable  Ship cycles will be shorter and more predictable  No backlog to carry from release to release  No backlog to carry from release to release  Cleaner code  Cleaner code  Consider refactoring  Consider refactoring  Techniques for quality improvement  Techniques for quality improvement  Do a ‘quality release’  Do a ‘quality release’  Implement a ‘bug jail’  Implement a ‘bug jail’ ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 10

Ability to Maintain your Service  Think about maintenance during the design  Think about maintenance during the design phase phase  Design for ease of deployment  Design for ease of deployment  Keep hardware/OS/software current  Keep hardware/OS/software current 20% Productive 80% 80% Non- Productive 20% ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 11

Investment in Infrastructure  Physical Infrastructure  Physical Infrastructure  Logging  Logging  Metrics  Metrics Test Case Development 1200 100% 90% 1000 80% 70% 800 60% Total Automated 600 50% Total Test Cases 40% 400 30% % Automated 20% 200 10% 0 0% Jan Beta Beta v.1.0 v. 1.1 v.1.2 v.1.3 v.1.4 06 1 2 ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 12

Employee Morale and Vitality  Long hours lead to  Long hours lead to  Low productivity  Low productivity  Job dissatisfaction/Burnout  Job dissatisfaction/Burnout  High turnover  High turnover  Mistrust of  Mistrust of management management ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 13

Strategy: Appropriate Rewards  Software development is a team sport  Reward successful teams ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 14

Tactics  Know best practices  Know best practices  Be polite but persistent  Be polite but persistent  Find your allies  Find your allies  Understand the real problem  Understand the real problem  Measure yourself  Measure yourself  Set clear goals  Set clear goals  Celebrate success  Celebrate success Most importantly, don’t give up! ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 15

Questions ___________________________________________________________________________________________________________________________ Copies may not be made or distributed for commercial use Excerpt from PNSQC 2011 PNSQC.ORG 16