What do you think of the new Periodic Table of Testing Version 3 and text list version?

It has taken me far too long but I’ve finally updated my Periodic Table of Testing and made it accessible by adding a text list version. As it has been 7 years since the last update I’d be grateful to hear your feedback on the latest version.

  • Are there any areas you think should really be included?
  • Are there any areas you think should be removed or replaced?

I hope to get round to updating the strategy article at some point on using the table to help scope projects. Maybe even the other related content as well. Anyway, hope to hear what you think. Thanks

4 Likes

Hi! This is my first time encountering this. I think it’s amazing!
Is this like an overview of everything about Testing? How unique and… vast! :shaking_face:

No one: You’re a Software QA? What do you do?
Me: * Shows Periodic Table of Testing * :nail_polish:

1 Like

This is also my first time seeing this :face_with_peeking_eye: what an incredible resource! I’ve bookmarked it and plan to use this as an input to my thinking for new onboarding materials and skill assessments… Thank you!

1 Like

wow Awesome.

Few questions

  • UB - userbility. Is this usability ?
  • PR Appears twice as Pairing once in Testing Element and in Personal Element. Do they mean same at both places

I see in description Communications* → PR – Pairing
What exactly is Pairing in communication ?

Also What is Customer tours ? journey i have heard

Good spot, hope Ady can clarify
I wonder if UserBility is a play on words, to make people think about usability by adding the word “user” in there.
PR, usually means Public Relations, that’s how I read it.

2 Likes

Thanks Susan, there are some other related articles on my website that you might find useful. The main one is on categorising the elements for projects but you can also use it to guide your training.

1 Like

Thanks Gaurav, you are the first person to spot that spelling error. Now corrected, thank you. I’ve tried to answer your other questions below but if you have any follow up questions or if anything isn’t clear please let me know.

It is that same thing but thought about from differnt perspectives. Under exploratory, pairing, whether with a dev, designer or other role, is used to discover information about the system or design. Code structure, logic, architecture, structure, intent etc.
Under comms (communication) it is about working with the other person, developing a rapport and building trust.

I hope that make sense and I’m aware there is some overlap for this and others that could be in different places.

Customer tours and journeys are probably a bit old fashioned these days as the focus is more on using personas. They are originally UX tools to outline how customers might use a product or feature. A journey is the total things a customer can do and their experiences with a product. A tour is like onboarding a customer. What are the things you would show them or guide them to when they first start. I applied them when using a persona to better replicate real-world interactions. So I’d pick a persona and take them on a customer tour or journey, before I did any exploratory testing using a persona, if that makes sense?

1 Like

Corrected the spelling error and changed PR to PA. Let me know if that’s better?