A grey coloured cat is saying MVP done while another hits it on the head replying, not if its no accessible!

Adaptable test design in software testing mostly sits in the exploratory testing world but can be applied throughout the testing process. It has various benefits such as increasing the speed of response to change and reducing cost. The term adaptable test design in software development refers to the practice of creating test plans, cases, and strategies that can be easily adjusted. Reasons for adjustments could be to accommodate changes in the project, such as new requirements, updated features, or shifts in priorities. It ensures that testing activities remain relevant and effective as the software evolves, especially in dynamic environments like Agile or DevOps. Adaptable test design is primarily applied to exploratory testing as part of its core, but it can also be applied to planning and risk based testing. It is about remaining flexible where possible and adapting to new priorities or knowledge. 

Ady Stokes wearing an MoT planet logo on the dock at the British Virgin Isles. There’s the from of a cruise ship in the background with the bay stretching across to a hillside.

Holistic thinking looks at the big picture to understand how parts contribute to the whole. It looks at the purpose and value of a feature or component rather than the specific mechanics of how it works. Holistic thinking works well for creating high-level strategies and this is where holistic testing comes in.

Systems thinking lets you step back from the detail to look at the whole holistically.I’d explain it by likening it to looking at an end to end process before diving into a specific part. Without knowledge of the whole you might focus on something while missing context or risks etc. One way I apply it in my current role is reviewing architecture documents to find areas of risk, ways and things to test as well as opportunities for automation and potential ways to use mocks and stubs to increase testability. In my current context it also allowed me to have early conversations about data and design.

System thinking is an approach for looking at the system as a whole rather than just the individual components. How do each feature or function interact, connect and contribute to the overall workings of the system? By viewing the whole system we can theorise that a change in one part may have unintended consequences.

Discover how testers can add value and improve quality by understanding and contributing to CI/CD pipelines

What is the most critical first step in setting up a testing function?

So, what is accessibility testing?Accessibility testing is about making sure digital products like websites and apps are usable by everybody. While it is a broad and complicated subject with lots to learn, accessibility testing can be as simple as making sure everything can be accessed and operated with a keyboard. One of the main routes to compliance are the Web Content Accessibility Guidelines or WCAG.  Do you have any examples?Let's start with some simple examples of accessibility testing for a web page. When the page loads, the keyboard focus should be at the top. If the page has a menu, whether across the top or down the side, there should be the option to jump or skip that menu to get directly to the content. Called a skip to main link, this option saves people who use a keyboard having to tab through the menus every time on each page. While you check that skip link, can you see where the keyboard focus is? Keyboard focus helps people understand where they are on the page they are navigating.  What are the benefits?There are many benefits from having accessible digital products. Accessibility testing helps companies by reducing the risk of legal actions and making sure as many people as possible can access their services. Ensuring your product or service is inclusive to people with disabilities opens up a potential new market you could be missing out on.  Are there any pitfalls?There are some pitfalls of accessibility testing that come up regularly. The myth that automated testing tools are all you need to ensure accessibility. Unfortunately, even using a combination of multiple tools, you can only cover around forty to fifty percent of all web content accessibility guidelines.A few other pitfalls include thinking it's a one time action, not part of the whole development process, not consulting a wide range of users for feedback, and that accessibility isn't part of the design. Great. So now we know about accessibility testing.

 A requirement is much more than something to check off a list; it’s a starting point for testing.

The testing community is multi-talented

Recognise the common signs of burnout, and explore practical strategies for seeking support and rebuilding well-being