For Wednesday of TestBash Manchester week, we’re exploring job titles and their definitions with @jitgo
Have you considered becoming a principal tester?
We’ll use this thread to ask questions and share resources from the talk. Remember that liking any questions already asked will increase the chances of them being answered live in the talk
Have you found, during lockdown, the “troubleshooter,” dropping into problem areas sort of role is a little more difficult? With colocation, obviously, you can go and sit with people.
Yes, because it seems so obvious why you’re there. But over time I’ve found that having a relationship with the team to be really beneficial as you’re already there when issues start to crop up.
If I understood it correctly, you don’t consider Quailty Engineers to be Coaches, because they do not have the coaching background. Are there any other reasons (because I feel this role would be called Quality Coach in other contexts)?
To me it sounds like the Quality Engineer works on things that could also be seen as responsibility of Scrum Masters / Agile Coaches or Senior Roles / Leads.
How would you see the realtionship between those roles?
Do you see it as part of the prinicpal testers role to help engineering teams tackle more socio-political issues that may be affecting testability at project levels? e.g. clarity of information coming to teams, deadline culture, lack of connection between delivery teams and key stakeholders…
You said the the Expert could do tasks of Junior Testers to Senior Testers in a team. This sounds a bit like a fireman. How long does a Principal Tester (Expert) typically stay with a team?
Hello from Brazil
Since you are not so focused in daily hands on, How do you find yourself catching up with new technologies and continuously being the expert of the group?
Thanks, great presentation!
yes, I can identify with the principal tester role.
Hanging out in the tech discussions is good.
Reviewing automation architecture also is something which I would see as part of this role
How are principle testers usually involved in reporting quality metrics to stakeholders who make decisions whether to promote a release candidate build to production or not? E.g are they often people who report that we should pull a hand-brake on a release because we have found bugs which prevent us from releasing the build or is it more of the job of the test manager?