T is for Testing? 
What else?
4 Likes
T is for Tribe, for two reasons.
The first is that, despite being a programmer rather than anything with Quality or Test in its job title, I feel like MoT is a tribe I feel at home in. I have learned a lot from the community, and felt welcomed. Thank you everyone.
The second is more generally useful to others, I think. You need to cultivate your tribe where you work. Hitting people over the head with “I’m not a gatekeeper to releasing”, “Developers can’t just chuck stuff over the fence to me - they’re responsible for quality too”, “I do more than just click buttons and follow test scripts you know” etc. are understandable reactions to many situations, but probably won’t be as effective as persuading people gradually and continually.
Meet people where they are and show how you can help them rather than just assuming the moral high ground. You probably won’t have influence over people by being a high ranking manager etc, so you need to develop influence in more person-to-person ways. It’s hard work, over a long time, but can be worth it.
3 Likes
T is for Triangle, like the famous*iron triangle ", used to describe delivering software projects, where we can choose only two from cost, quality and speed. Or the automation triangle, a model much used and remodelled.
1 Like
T is for Trust.
Trust zones, used in threat modelling, a part of security testing.
Trust, like the kind we need to gain with our teams, so we can deliver important news without I being ignored.
Trust, like the kind we need to build with our customers, by making sure we treat them, their data, privacy, security, safety and time with respect.
2 Likes
T is for Thinking.
Because, by being thoughtful we can improve quality, build communities and make better software.
2 Likes
T of for temperament
Anyone can “test”, but not everyone can test effectively. Many skills are required. Yes, some aspects can be learnt, but having the right temperament is something you have or don’t. This leads onto…
T of for tenacity
As testers, we have to be tenacious. Defects are rarely obvious; it takes persistence and a systematic approach to uncover those buried gems!
3 Likes
- Threat Modeling
- Timeboxing
2 Likes
T is for Together
from different perspective: within the testing team and working with other teams.
Within the testing team: A team work has better results than several individuals. the brain storm and progress together produce better idea to explore.
Working with other teams: being together with Architects and Developers make your work more significant. working together for a better quality.
3 Likes
T is for testers
T is for team which is in almost every organization
T is for a thread of communication for e.g. email thread
T is for test-design, test-planning, test-strategy, etc.
T is for talking which testers should do regularly with developers
T is for time which is consumed in testing
T is for testbash
1 Like
Thread
Trend
Tackle
Topic
T is for Toyota for whom quality is so important and from whom we can all learn. Useful books on Toyota:
- The Toyota Way by Jeffrey Liker
- The Machine That Changed the World by James P. Womack, Daniel T. Jones and Daniel Roos
- Learning to Lead, Leading to Learn by Katie Anderson and Isao Yoshino
I learned about small batches from Toyota: Why we should work in small batches – a story from Japan – TestAndAnalysis
2 Likes
T is for Theory of Constraints.
2 Likes
Test
Think
Threat
Team
Trust
Transform
Threshold
Time
Transact
Tuple
Testability
Tech stack
Tech debt
1 Like