Skip to content

Commit

Permalink
Updated Our Differentiated Approach To Testing
Browse files Browse the repository at this point in the history
  • Loading branch information
pauldykes authored and Siteleaf committed Oct 30, 2024
1 parent 735bc6f commit 3d9f7ab
Showing 1 changed file with 9 additions and 2 deletions.
11 changes: 9 additions & 2 deletions _drafts/our-differentiated-approach-to-testing.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -17,21 +17,28 @@ Scott Logic has been delivering change and providing expertise to clients in pri

## 1) Understand the Context

We know that testing cannot be standardised. Businesses, customers, products and the risks and challenges they face are not standardized, so testing shouldn’t be either. We start any testing activity by developing an understanding of the technology, its purpose, and the people it serves. This gives us the foundations to deliver excellent testing in the right way.
We know that testing cannot be standardised. Businesses, customers and products are not standardised, nor are the risks and challenges they face, so testing shouldn’t be either. We start any testing activity by developing an understanding of the technology, its purpose, and the people it serves. This gives us the foundations to deliver excellent testing in the right way.

## 2) Value in tooling
We have extensive experience with tools and automation frameworks, and this has given us practical insights into their benefits. We look for opportunities to use automation to provide rapid, repeatable checks and to expand coverage. Our experience with tools is broad and deep, covering many types of testing tools including those for Performance, Accessibility, Compatibility and API testing. To understand the value of tools and automation, we balance their benefits with the cost and effort of establishing and maintaining them. Only then can we take an agnostic and holistic approach in recommending the most suitable tools for testing.

We have extensive experience with tools and automation frameworks, and this has given us practical insights into their benefits. We look for opportunities to use automation to provide rapid, repeatable checks and to expand coverage.

Our experience with tools is broad and deep, covering many types of testing tools including those for Performance, Accessibility, Compatibility and API testing. To understand the value of tools and automation, we balance their benefits with the cost and effort of establishing and maintaining them. Only then can we take an agnostic and holistic approach in recommending the most suitable tools for testing.

## 3) Quality for humans

The platforms, applications and other products we work on exist to serve people. We apply technical skills and knowledge in our work, and strive for excellence in what we deliver, but regardless of the tools, techniques and infrastructure we use, we recognise that ultimately it is people who will decide whether the products they use give them what they need, are helpful and whether they want to continue using them. Therefore, we keep people in mind when we test. We understand that their needs are diverse, and their perceptions of quality are subjective and variable. We think about the ways technology could help them, how it could hinder them and how it could fail them.

## 4) Risks over Requirements

We have a deep understanding of the kind of risks that organisations and teams face. These help us to tailor an approach to testing that helps you to understand those risks and identify problems as early as possible. We will not assume that requirements, stories or acceptance criteria have been prepared with all the risks in mind. Testing coverage based solely on requirements inherits any gaps or assumptions, so we will test beyond requirements, exploring risks and seeking out potential problems in the product.

## 5) Bring a testing mindset

Testers often bring a unique mindset to a team, applying curiosity and critical thinking along with a team ethic and desire to help improve quality. A strong sense of collaboration, and a desire for the project to succeed is coupled with a willingness to question. This constructive scepticism provides colleagues and clients with a different perspective, and helps the whole team identify opportunities to improve the product. We consistently apply this mindset in our work.

## 6) Collaborate and cross-skill

We believe that testers are not gatekeepers, or the sole advocates for quality. Industry development practices which often encouraged testers to operate independently from the rest of the team have thankfully been replaced with a recognition that collaboration and continuous testing are valuable. To contribute within a high performing development team, an understanding of the skills of others is hugely helpful. Our testers bring a range of technical skills which complement their testing mindset. They understand that knowledge of design, coding and other crafts can improve their testing. Meanwhile, they share testing expertise with others, helping them to test designs, code or even their assumptions.

These principles provide a framework for excellent testing, and a broader view of quality. Our consultants bring experience and skills across a wide range of contexts and understand that products benefit from continuous evaluation. We don’t simply ‘shift left’ into design and build, or ‘shift right’ into production monitoring. We look for opportunities throughout a product’s life to investigate and provide valuable information to Product Owners, Development teams and other important stakeholders. Whether for new products, features or maintenance and changes, we work hand in hand with the wider team to make sure that testability and quality are given focus throughout development, delivery, operation and maintenance.

0 comments on commit 3d9f7ab

Please sign in to comment.