2. Agenda
Presenter
Quality & QA
DEV Lifecycle
Cost of quality
Technical debt
Issues
Git, CI, Sonar, Se
Bottom line
Thanks
3. Ady Beleanu
• Quality inquisitor
• 10 years in field of QC & QA
• Managed projects & teams
• Coached & inspired testers
• https://www.linkedin.com/in/adybeleanu
4. Quality
Quality (ISO) = The totality of the characteristics of an entity
that bear on its ability to satisfy stated or implied needs
“= ability of product to be able to satisfy end users”
The concept of making products fit for a purpose.
Minimising defects and problems.
You - feel it!
6. Quality Focus – Final product
Added value
Attention to detail
Process behind the product Innovation & Pioneering
Both – from point A to point B
the difference - usability, safety, comfort, reliability, and so
on
vs.
7. Quality Assurance – The Pieces
For the system to work, each piece has to be:
Perfect
Easily integrated
Tested
Reusable
vs.
8.
9. Key Success Criteria
THE BIBLE of the project
• Business case
• Architecture
• Requirements
• Quality strategy
• Project Synchronization
“Establishing your Automation Development Lifecycle”, Galen
20. Problem no.1 – Code Quality
http://www.bonkersworld.net/code-reviews/
Poor unit test coverage Complexity for integration test
No full regression (100%) Tight couplings
21. Why code review?
Find bugs early / Fix cheap
Coding standards compliance
Sharing knowledge
Consistent design and
implementation
Higher software security
Team cohesion
Confidence of stakeholders
24. Context – project done with & without code review:
10k LOC,
10eng,
3month project
Measured # of bugs found by QA Team in the next 6
months
The result: Code review would have saved half the cost of
fixing the bugs. Plus, they would have found 162 additional
bugs.
Code Review – Case Study
27. Code Review - trend & numbers
2012 study (VDC Research)
• 17.6% software engineers surveyed currently use automated tools for CR
• 23.7% expect to use them within 2 years.
Capers Jones' - 12,000 SW dev projects:
- 60-65% - The latent defect discovery rate of formal inspection.
- < 50% - For informal inspection.
- 30% - The latent defect discovery rate for most forms of testing.
150 lines of code per hour - Typical code review rates.
Code reviews => ~85% defect removal rate (avg. rate of about 65%)
75% of CR defects evolvability rather than functionality
suitable for long product / system life cycles => increase of Technical DEBT.
30. Continuous Inspection with SonarQube
7 Deadly Sins of source code
Duplications
Bad distribution of complexity
Spaghetti Design
Lack of unit tests
No coding standards
Potential bugs
Not enough / too many comments