How Management See Testing
How Management Would Like To See Testing
Responding to change overfollowing a plan
Testers in an agile team
AutomatedFunctional / Specialist Tests
more testing involvement
Testers need more
Analysts need more testing involvement
Testers in an agile team
(noun) the standard of something as measured against other things of a similar kind; the degree of excellence of something
Image: http://www.naccho.org/topics/infrastructure/accreditation/images/Quality-Definition.jpg /
Definition of Quality…
Quality means different things
What does quality mean to the different roles in the team?
What are quality attributes?
How do we know what quality attributes to include?
What are risks with the quality attributes we are trading off?
How do we test and measure quality?
How does quality relate to the sliders?
What does quality mean?
How do we apply quality to our work
Software is a Series of Loops
End to end automated tests and cover 10 conditions per
test, manual covers 1 condition per test
Automated tests cover all high priority business flows,
manual tests mostly cover lower priority flows
Metrics need context!
% Regression test cases automated
Testing is more than a series of merely repeatable actions
No agreed approach to testing
Tests are not considered a valuable asset
An agreed approach to testing that is aligned to a definition of quality
Tests are considered a valuable asset that can be reused as features are progressively implemented
Test strategy is agreed and understood by the team and includes targets (coverage, defects, …)
Test strategy is documented and visible as a BVC used by the team
Non-functional requirements are agreed and included in the test strategy
Test planning is based on risk (technical complexity and business impact)
Test artifacts are treated with the same importance as code and are properly maintained and refactored
The relevant ____ilityand security tests form part of the test strategy
Automation: I work with developers to automate tests that provide business value and identify system risks
Collaboration: I work with analysts and SMEsto ensure that testable acceptance criteria are created for all stories
Strategy & Planning: I am involved in the project at all stages to ensure that testing provides the greatest value and quality objectives are achieved
Tools & Techniques: I use both manual and automated techniques using the preferred testing tools based on the situation
Architecture: I have an understanding of the system architecture and can create tests that verify individual components and the system as a whole
Development: I take an interest in development practices and monitor code quality metrics
Estimating: I am involved in developing estimates for projects at a story level, for tools and infrastructure and also for deployment/release activities
Reporting: I provide metrics that give insight into project health and system quality
Agile: I understand Agile project delivery and the differences between testing in the different phases of an phase
Qualifications & Training: I have recognised qualifications in testing and continually update and maintain my skills
Recruitment & Development: I am attracted to the organisation because testing is a cool career path that offers heaps of opportunities and a way of continually developing my skills
Community & Teams: I am part of a community of testers that are embedded within teams but share common values
Command Line Interface
Capture Replay (Selenium)
Test Maintenance & Data
Specification By Example / ATDD / BDD
Test Automation Course
New Software Test Engineer Role
New Graduates, Recruits, Consultants & Partners
Current Test Analysts
Capable + Current Skills + Desire
Capable + Desire
Not Capable + No Desire
Not Capable + Desire
**Assessment = Technical Test + Interview**
Assist & Assess
Get Involved Early
Queue to Join
Speed to Cool
Build / Compile
Run Tests / Analysis
Stop The Line!
Iterative was only the beginning!