Skip to main content

Getting started with testability



At TestBash Netherlands, I said that, in my experience, a lot of testers don't really get testability. I would feel bad if I didn't follow that up with a starting point for expanding your mindset and explicitly thinking about testability day to day, and making your testing lives better! 

In large scale, high transaction systems testability really is critical, as compared to the vastness and variability of the world, testing done within organisations, before deployment, is limited by comparison. We need ways to see and learn from the systems we test where it matters, in Production.

Being able to observe, control and understand is central to testing effectively, and there are loads of resources and experience reports out there to help. I was/am inspired by James Bach, Seth Eliot, Matt Skelton, Sally Goble, Martin Fowler and a little bit of PerfBytes/Logchat, so lets see if it works for you! 

Overall Model:

Heuristics of Software Testability by James Bach

http://www.satisfice.com/tools/testable.pdf

In particular, the intrinsic testability of a system. I firmly believe that a system with high testability has high supportability in this regard. If you could build a system that gave those with operational responsibility with the ability to observe, control and understand what was happening, they would be stoked right? 


Videos:

Seth Eliot introduces testing in production with some compelling examples


Sally Goble then talks about shifting testing away from current models and leveraging production:

Articles:

Perfect Testing 

Feature Toggles

https://martinfowler.com/articles/feature-toggles.html

Rethinking Pipelines



Data Driven Quality

Signal vs Pass/Fail

Ask for Testability - Interesting Idea on Scriptable API's to drive the product

http://www.developsense.com/blog/2014/05/very-short-blog-posts-18-ask-for-testability/

A Map for Testability - Visualising testability in early product conversations

http://www.a-sisyphean-task.com/2014/07/a-map-for-testability.html

Putting Your Testability Socks On - Analysis of the SOCKS testability mnemonic

http://www.a-sisyphean-task.com/2012/07/putting-your-testability-socks-on.html

Audio:





Comments

  1. Good post! Software testability is integral part of a software development. If a software is not testable it is of no use for the organisation.

    ReplyDelete
  2. This comment has been removed by a blog administrator.

    ReplyDelete

Post a Comment

Popular posts from this blog

Testers Guide to Myths of Unit Testing

One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers, and help us realise what other layers of testing can cover most effectively.

Also, I want to do a talk about it, so I figured I would test the premise, see if potential audiences were into it. I put this on Twitter:
Working on a talk about what testers might believe about unit #testing & how we interact with developers creating unit tests. Any challenges/additions for my list below? #development#agilepic.twitter.com/4oT5HE4qs3 — Ash Winter (@northern_tester) December 19, 201730 replies with ideas tends to indicate that people might be into it. 
The ListI thought, as my final blog of 2017, I would provide a super useful list of the myths and legends we as testers might believe about unit testing:
That developer…

Wheel of Testing Part 2 - Content

Thank you Reddit, while attempting to find pictures of the earths core, you surpass yourself.
Turns out Steve Buscemi is the centre of the world.

Anyway. Lets start with something I hold to be true. My testing career is mine to shape, it has many influences but only one driver. No one will do it for me. Organisations that offer a career (or even a vocation) are offering something that is not theirs to give. Too much of their own needs get in the way, plus morphing into a badass question-asker, assumption-challenger, claim-demolisher and illusion-breaker is a bit terrifying for most organisations. Therefore, I hope the wheel is a tool for possibilities not definitive answers, otherwise it would just be another tool trying to provide a path which is yours to define.


In part one, I discussed why I had thought about the wheel of testing in terms of my own motivations for creating it, plus applying the reasoning of a career in testing to it. As in, coming up with a sensible reflection of real…