The document discusses non-functional testing (NFT) and provides advice on common issues, managing risk, and areas for improvement. It notes that NFT is often poorly defined, planned, and executed. It recommends fostering common understanding of NFT, engaging stakeholders early, setting clear test catalogs, and integrating NFT into design, development, and monitoring. The document also provides the author's experience and contact information for consulting services.

1. NON FUNCTIONAL TEST
MANAGEMENT
Martin Croft
06/09/2016

2. Martin Croft:
18 Years experience in non functional
testing.
Verticals including Banking,
Communications, Broadcast, Publishing,
GIS.
Mostly mission critical technology upgrades
and new product go lives.
Lets run through some common issues with
NFRs and areas where improvements can be
made
• Common Issues
• Managing the risk
• Improvement areas

3. Common Issues with NFT
• “NFT" is often inconsistently defined across DEV and
Business
• Quality of NFRs to be tested against may be poor
• Lack of suitable test environments and test data
• NFT poorly planned
• Quality of business volumetrics used to define NFRs is
• often poor
• Lack of understanding or interpretation of Analytics
• Poor use of tools
• NFT is more than just performance testing

4. Managing the Risk
• Foster a common understanding and definition of NFRs
• Build NFRs from direct experience in production
• Use performance engineering techniques within
development
• Understand how your users actually use your product
• Engage with vendors early around NFRs
• Pre production environments should be under the same
control as production
• Get Dev opps involved early to ensure server builds are
tested consistently with NFRs
• Build relationships with Architects, DBAs, Network
teams and Dev Opps

5. Improvement Areas
• Set out a clear catalog of NFRs and their relevance and
ownership
• Use BDD stories to bring NFRs into design and
development
• Extend NFT to include resilience, security, Usability and
support
• Monitoring and analytics should be close coupled
• Frequent reporting on the status of NFRs
• Performance, recovery and resilience scenarios run
within CI
• Scan for security vulnerabilities early
• Engage with operations teams early

6. My Work
• Engaged as a consultant for project
work
• Mentoring staff via training or consulting
days
• Work with project teams to define NFRs
• Performance testing, tool selection and
training

7. Contact:
Email: Consulting@selectred.com
Mobile: 07515 352 448
LinkedIn:
https://www.linkedin.com/in/selectred