Embed Size (px)
DESCRIPTION
Development Testing – Is It Worth It?. Arthur Hicken September 2012. GoToWebinar Housekeeping. Your Participation. Open and hide your control panel Join audio: Choose “ Mic & Speakers” to use VoIP Choose “Telephone” and dial using the information provided - PowerPoint PPT Presentation
Citation preview
Development Testing – Is It Worth It?
Arthur HickenSeptember 2012
Open and hide your control panel
Join audio:• Choose “Mic & Speakers” to use
VoIP• Choose “Telephone” and dial
using the information provided
Submit questions and comments via the Questions panel
Note: Today’s presentation is being recorded and will be provided within 48 hours.
Your Participation
GoToWebinar Housekeeping
Parasoft Proprietary and Confidential
About Parasoft
Founded in 1987 Runtime Error Detection in 1993 Static Analysis tools since in 1994 Automated Test Generation in 1997 Development Testing Platform in 2003 Automated Defect Prevention published 2007 Automated Defect Prevention: Best Practices in Software
Management published 2007 27 Patents for automated quality processes Build quality into the process
Parasoft Capabilities
Technologies Quality Policy Management Task Management Code Analysis – Pattern Based Code Analysis – Flow Based Code Analysis - Metrics Code Review Unit Testing Framework Memory Error Detection Runtime Analysis Message/Protocol Testing Application Behavior Emulation Functional Testing Load Testing
Parasoft Proprietary and Confidential
What is Development Testing?
What is it? Best practices Processes Infrastructure Desktop Policy and Business needs
What Development Testing is Not A replacement for QA Simply a shift of the test process A silver bullet
6
Aspects of Development Testing
Development Best Practices in place Requirements Traceability / Compliance / Audit Static Analysis Peer Review Unit Testing Source Control Integration Developer IDE Integration Automated / Continuous build Metrics Workflow Infrastructure
Parasoft Proprietary and Confidential
7
Isn’t QA Enough?
Development Testing begins where QA Ends Or vice-versa
Policy driven Process oriented Engineering focused Focus on Prevention
Parasoft Proprietary and Confidential
Why Prevention? The Cost of Errors
Why Prevention? The Cost of Errors
10
An Ounce of Prevention
Early Detection is… Better than Just Q/A Detection != Prevention
Feedback loop Frequent issues from Peer Review Field reports QA findings
The misunderstood relationship between flow analysis and pattern-based static analysis
Creating a software environment where bugs cannot survive.
Parasoft Proprietary and Confidential
Plan and manage your project fulfill customer requirements precisely distribute work and resources predict whether your plan is feasible to meet deadlines
Monitor and manage progress have instant access to the status and evidence of risks of current projects
Comply follow project / organization policies adhere to best industry practices fulfill contractual obligations
Certify and Audit provide traceability to fulfill certification criteria
(ISO-x, FDA, DO-178, IEC-x, etc.) decrease certification cost support standards like MISRA, JSF, etc.
Improve optimize products and processes based on historical data (post-mortem analysis) increase efficiency, performance and utilization track down where your cost is located
Management and Traceability
Monitor/Manage Processes: Manager Dashboard
Parasoft Proprietary and Confidential
13
Policy - Is It Working?
Setup policies Test Coverage Unit Tests Executed SA Compliance Peer review expectations Measure – Monitor - Improve
Base threshold on current results Incremental improvement
Parasoft Proprietary and Confidential
Static Analysis
Variety of methods Peer Review / Manual Code Review / Code Inspection Pattern-based code scanners Flow-based code scanners Metrics-based code scanners Compiler / build output
Parasoft Proprietary and Confidential
SA for Process Improvement
Flow rules have corresponding pattern-based rules Prevent the potential rather than chase paths Analyze issues and select SA based on real problems Analyze flow-analysis issues and select pattern rules to
prevent
Parasoft Proprietary and Confidential
Peer Review
Great for mentoring Great for conceptual work Avoid formatting & other
things the computer can do
Parasoft Proprietary and Confidential
Metrics
KLOC Complexity Maintainability Index Numbers (files, lines, methods)
Parasoft Proprietary and Confidential
Monitor/Manage Processes: Tests Overview
Parasoft Proprietary and Confidential
Trend Reporting
Reports should show violations Show trends Breakdowns
File Violation type Severity developer
Parasoft Proprietary and Confidential
Parasoft Proprietary and Confidential
Results within IDE
1 Results delivered as uniform view within IDE
2 Directly access line of code to fix
3 Check-in
21
Workflow
Plan processes Audit trail Ingrain expected behavior
Parasoft Proprietary and Confidential
Sample SDLC & Integration
RMS/BTS/SCM integrated – easy collaboration
Task Management System – all activities in one common list of tasks
Automated and Manual Tests, Automated Code Review
Traceability from Requirements, Defects, Tasks to Tests and Source and Code Review
Automated Notification
Prioritized tests based on changes
Extensive reports for CIO, Stake Holders, Project Managers
AUTOMATICTEST
SERVERS
CIOPROJECT
MANAGERMS
PROJECT
QA TEAM
BTS SOURCECODE
DEVELOPERS
DEVELOPERSRMSREQANALYST
23
Should I Care about Development Testing?
Why pay attention today? Moving goal posts Agile development Ad-hoc tool usage will not get the job done
Parasoft Proprietary and Confidential
Q&A / Further Reading
Parasoft Proprietary and Confidential
Automated Defect Prevention (Huizinga & Kolawa)
…Principles and processes to improve the software development process.
Effective C++ / More Effective C++ (Meyers)
…Definitive work on proper C++ design and programming.
Effective Java (Bloch)
…Best-practice solutions for programming challenges.
Design Patterns (Gamma, Helm, Johnson, Vlissides)
…Timeless and elegant solutions to common problems.
