What is Testability?
-
Unlocked
Richard Bradshaw
Mark Winteringham
Tester, Toolsmith, Author and Instructor
Talk Description
Learn all about Testability. What it is, why it's valuable and what to keep in mind when analysing testability
Richard Bradshaw
Richard Bradshaw is an experienced tester, consultant and generally a friendly guy. He shares his passion for testing through consulting, training and giving presentation on a variety of topics related to testing. He is a fan of automation that supports testing. With over 10 years testing experience, he has a lot of insights into the world of testing and software development. Richard is a very active member of the testing community. Richard blogs at thefriendlytester.co.uk and tweets as @FriendlyTester. He is also the creator of the YouTube channel, Whiteboard Testing.
Mark Winteringham
Tester, Toolsmith, Author and Instructor
Mark Winteringham is a tester, toolsmith and author of AI-Assisted Testing and Testing Web APIs, with over ten years of experience providing testing expertise on award-winning projects across a wide range of technology sectors, including BBC, Barclays, UK Government and Thomson Reuters.
He is an advocate for modern risk-based testing practices and trains teams in Automation, Behaviour Driven Development and Exploratory testing techniques. He is also the co-founder of Ministry of Testing Essentials a community raising awareness of careers in testing and improving testing education.
You can find him on Twitter @2bittester or at mwtestconsultancy.co.uk
00:00:05,680: Hi, Richard. So what's testability?
00:00:08,245: For me,
00:00:08,725: testability is a measure of how easy it is for testing to
00:00:11,925: happen in a given context.
00:00:13,845: Testibility is a measure of many drivers such as people,
00:00:17,540: product, vision, process, time, resources, and problem.
00:00:21,620: These drivers can have a positive effect on our testing,
00:00:24,260: making it easier to test,
00:00:25,835: or they can have a negative effect to making it more
00:00:28,075: difficult to test. Interesting. So do you have any examples?
00:00:31,915: Yes.
00:00:32,235: The team's attitudes toward testing can either mean testing
00:00:35,080: prioritize and supported, or it's an afterthought.
00:00:38,600: A product with many accessible layers such as APIs means we
00:00:42,040: can be more targeted with our testing and automation.
00:00:45,545: Access to testing tools could be restricted due to budget or IT policies.
00:00:49,625: This impacts the types of testing we'll be able to do.
00:00:52,590: And what's the value of knowing about testability?
00:00:55,710: Knowing about testability informs our testing approaches
00:00:58,510: and our strategies.
00:00:59,955: It provides clear framing for the testing we do and don't do,
00:01:03,555: which helps communicate that work to others,
00:01:06,515: improving testability often delivers more value to the team
00:01:09,770: than doing more testing activities.
00:01:12,090: And what are some of the pitfalls around testability?
00:01:15,475: Testability is fluid. Therefore,
00:01:17,235: teams need to periodically review it to ensure approaches
00:01:20,035: are fit for purpose.
00:01:21,555: As testability is an assessment of contact drivers,
00:01:24,290: it can often be biased by those doing the measuring.
00:01:26,930: So it's important to include the whole team. Great.
00:01:29,890: So now we know about testability.
00:00:08,245: For me,
00:00:08,725: testability is a measure of how easy it is for testing to
00:00:11,925: happen in a given context.
00:00:13,845: Testibility is a measure of many drivers such as people,
00:00:17,540: product, vision, process, time, resources, and problem.
00:00:21,620: These drivers can have a positive effect on our testing,
00:00:24,260: making it easier to test,
00:00:25,835: or they can have a negative effect to making it more
00:00:28,075: difficult to test. Interesting. So do you have any examples?
00:00:31,915: Yes.
00:00:32,235: The team's attitudes toward testing can either mean testing
00:00:35,080: prioritize and supported, or it's an afterthought.
00:00:38,600: A product with many accessible layers such as APIs means we
00:00:42,040: can be more targeted with our testing and automation.
00:00:45,545: Access to testing tools could be restricted due to budget or IT policies.
00:00:49,625: This impacts the types of testing we'll be able to do.
00:00:52,590: And what's the value of knowing about testability?
00:00:55,710: Knowing about testability informs our testing approaches
00:00:58,510: and our strategies.
00:00:59,955: It provides clear framing for the testing we do and don't do,
00:01:03,555: which helps communicate that work to others,
00:01:06,515: improving testability often delivers more value to the team
00:01:09,770: than doing more testing activities.
00:01:12,090: And what are some of the pitfalls around testability?
00:01:15,475: Testability is fluid. Therefore,
00:01:17,235: teams need to periodically review it to ensure approaches
00:01:20,035: are fit for purpose.
00:01:21,555: As testability is an assessment of contact drivers,
00:01:24,290: it can often be biased by those doing the measuring.
00:01:26,930: So it's important to include the whole team. Great.
00:01:29,890: So now we know about testability.
Suggested Content
Explore MoT
Wed, 11 Sep 2024, 6:00 PM
Keysight are the proud sponsors of our pre-TestBash meetup by the beach
Gain the tools you need to become an operability advocate. Making your testing even more awesome along the way!
Debrief the week in Testing via a community radio show hosted by Simon Tomes and members of the community
