|
Nand32 wrote: ...had asked him to lower the flags. He goes back and updates the ticket.
Adjust the bug tracking software to only allow him to report findings, not assign them a priority.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
I think he needs to understand his job role and responsibility then.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
Hmmm,
I am a Poacher turned Game Keeper in my current role (I got a Job as a Tester as I got fed up with Daytime television). In my experience, if I don't know the dev. well I tend to wander over to his desk and say 'I am doing something stupid but...' it tends go over better than 'You don't know what you are doing butt head', then I log it in the bug tracking tool as you don't want a project with a huge back log hovering. If it's a quick fix (like spelling a word wrong on the interface, happened this am!) tell them, don't raise it as a fault, raise it as an observation.
|
|
|
|
|
 You can make a great test lead. 
|
|
|
|
|
Not sure if I want the stress... 
|
|
|
|
|
That is why you need to have a good work process and compartmentalize roles.
In your situation, I would get the tester and go to your product manager and discuss the issue.
We do that often when we're not certain of a bug importance or priority.
I'd rather be phishing!
|
|
|
|
|
I'm the conflict resolution point. Both report to me. The tester is bit of an attention seeker.
|
|
|
|
|
LOL this is one of my favourite subjects Not just everything you've said, but the emails 30 minutes later with all of your managers CC'd in asking if there is "any progress?" Then there is "tester driven design" where rather than ensuring the ticket meets the specs, they'll raise an issue if it does something they think it shouldn't, or doesn't do something they think it should.
"I've failed this because the widget doesn't highlight when hovered over"
"I've checked the specs and the acceptance criteria, and gone over my meeting notes, and I don't see that listed as a requirement?"
"I know, I just think it should highlight when hovered over"
*30 mins later*
"ANY PROGRESS ON THE CRITICAL BUG I RAISED ABOUT THE LACK OF HOVER????"
Then there is the constant interruptions if they've found a bug. If you find a bug log it in the tracker, I don't need you to stop me from what I'm doing to show me that when you click this button with the textbox empty that you get an error. Just raise it in the tracker.
Then to cap it all off, when bugs gets missed and make it live do the testers ever get any blow-back or criticism? Nope....
I've straight up not renewed a contract as I couldn't stand the testers.
|
|
|
|
|
Just one nonsensical character can trigger a whole lot of chain reactions. At times exposing all the other nonsensicals in the circle. 
|
|
|
|
|
Just as it's not the tester's role to assign users or priority to bugs it's not your role to put the tester in place.
Discuss the issue with your team lead, product owner, manager or whatever you have above you and let them handle it.
In the meantime, ignore the tester and pick up bugs and stories that have been approved through the regular process.
Unless, of course, the tester is in fact your CEO
|
|
|
|
|
Quote: Just as it's not the tester's role to assign users or priority to bugs it's not your role to put the tester in place.
hehe I'm the Lead, both the testers & devs reporting to me.
|
|
|
|
|
Then YOU should know whether the tester is out of line and if you think he is YOU should be the one to do something about it! 
|
|
|
|
|
Sounds like you are not doing your job then. As Sander it is up to you to lead your teams, you are the one who needs to assign priorities.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
That tester needs to be tied up and gagged !
|
|
|
|
|
And then tickled with a feather
|
|
|
|
|
Jörgen Andersson wrote: And then tickled with a featherchainsaw
FTFY
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Nand32 wrote: These are critical bugs fix it ASAP
This sounds like my users/testers! To them everything is critical. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
If you have a product owner for the project, then they should be responsible for prioritising which bugs get fixed when. They are the product stakeholders and should have the final say in a bug's priority. The testers therefore should liaise with the product owner, not the developers. Once the product owner has assigned the relevant priority to a bug, then the appropriate developer can fix it.
In the absence of a product owner, then another similar person who can represent the product or the business will be sufficient.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
I think a tester isn't in the position to issue commands. A tester has to deliver information with the project lead being the one issuing commands in response to the information.
|
|
|
|
|
My 2 cents.
All "bugs" are issues.
Not all "issues" are bugs.
A bug being something of unintended outcome.
Unless the tester is viewing the innerds of the program, I would find it difficult to assert that an issue is a bug.
Raise issue, let the issue process assign priority and severity.
|
|
|
|
|
Some testers (QA folk) think they are project managers - and these people are a detriment to delivering a quality product on time.
Others understand their role in a team delivering a product, and work as cooperating team members, focusing on how well their tests cover the code's functionality and the user's potential input. These folks are an invaluable asset.
IMHO, on a development team, the QA person should be involved to some degree (as a non-developer) during development so they are better prepared when testing starts, but should report to the team lead, who (again, IMHO) is a senior-level software engineer with solid business, communications, and leadership knowledge, skills, and abilities.
|
|
|
|
|
Yes. let's quit pretending the email is a legitimate bug tracking tool.
This should be entered in whatever tool you use to track the change to begin with.
You can choose to keep the current ticket open and add to it (fewer things to track, but multiple problem reports make it confusing) or open a new ticket for each reported problem, tying it back to the original change request.
I'd argue that QA shouldn't even be assigning these things, but that might be a bit much. Probably want to have the original developer investigate any fixes.
Also, someone has to be able to shut QA down if the perceived problem is actually a new change. "I found/thought of something that's not in the requirements, it's a bug!" might not be so. If it hinders use of the tool, then yes, it should be addressed. If it's just a "nice to have", it's an enhancement for future development.
|
|
|
|
|
Sounds lik a resounding reason to thoroughly test one's own code!
CQ de W5ALT
Walt Fair, Jr.PhD P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
I had a similar situation back in the 90's with a fairly senior tester. He would report bugs like this, but he would also not provide any clear way to reproduce the issue. I would get this problem report, try and reproduce it and find it all working.
So I would kick it back to him as "no repro" and ask for the steps to reproduce. Instead I just got vitriol and the bug punted back to me to fix.
In these sort of cases, it is up to management to provide a clear mechanism to decide on issues and priorities. Nowadays we tend to have sprints where the tasks are decided, including features and issues to be addressed. Only real show-stoppers can get added mid-sprint, and that still has to go through some sort of review.
To all the people in QA (I used to be one): Issues need to be investigated. Reduced to the smallest common repro steps. And any insights as to the issue is helpful. The more info you can provide, the easier you make it for development to figure out what is wrong and address it.
|
|
|
|
|
A horse walks into a bar and orders a pint.
The barkeep says "You're here pretty often. Do you think you might be an alcoholic?"
The horse replies, "I don't think I am," and vanishes from existence.
See, the joke is about Descartes' famous philosophy of 'I think, therefore, I am', but to explain that part before the rest of the joke would be putting Descartes before the horse.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
