MENU
Which are three attributes of a bad bug report?
Suggested Answer: A, B, C
Get Premium PSD Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
you don't want to blame anyone, have vague titles of make vague statements. It needs to be clear and constructive, and focussed on one specific problem. It should als not contain feature requests.
30 comments · newest first
SU
Sue
6 months ago
Yeah, and simple reproduction steps help a lot!
EL
Eladia
6 months ago
One bug per report is crucial for clarity.
ET
Ettie
6 months ago
I agree, vague statements lead to misunderstandings.
RI
Ricarda
6 months ago
Generic titles confuse everyone.
LA
Lanie
7 months ago
Definitely! Assigning blame just makes it worse.
LA
Lamar
7 months ago
Vague statements? That's like asking for confusion!
CA
Cassie
7 months ago
Generic titles just make it harder to find issues later.
CH
Chaya
8 months ago
Wait, are we really saying one bug per report is bad?
JO
Joesph
8 months ago
Totally agree, blaming others doesn't help!
AN
Annalee
8 months ago
Ah, the joys of debugging code based on a bug report that reads like a Shakespearean sonnet.
KE
Keva
8 months ago
D and E? Psh, those are for amateurs. Real pros make their bug reports as cryptic as possible.
TR
Trevor
8 months ago
I'd add "Lack of coffee stains" as a fourth attribute. How else will the devs know it's a real bug report?
BE
Beckie
8 months ago
Vague statements, assigning blame, and generic titles - the holy trinity of bad bug reports!
CL
Clorinda
9 months ago
A, B, and C are the correct attributes of a bad bug report.
KA
Kati
9 months ago
I feel like one bug per report is a good practice, but I’m not entirely confident about the other options.
ST
Stevie
9 months ago
Generic titles seem like a big issue too, but I can't recall if they were always listed as a top three in our practice tests.
HO
Hollis
9 months ago
I remember practicing a question like this, and I think assigning blame is definitely a bad attribute.
TY
Tyra
9 months ago
Hmm, I'm a little confused on this one. I know simple and repeatable reproduction steps are good, but I'm not sure if the other options are all bad. I'll have to review my notes and make sure I understand the key differences.
AL
Alesia
9 months ago
Easy peasy! Vague statements, assigning blame, and generic titles are the three bad attributes. I've seen enough bad bug reports to know those are the classic no-nos. Time to put that knowledge to use.
CO
Corrinne
10 months ago
A) and C) are definitely bad attributes.
KE
Kendra
10 months ago
I think vague statements are a big issue.
HE
Herschel
10 months ago
I think vague statements definitely make a bug report bad, but I'm not sure about the others.
MO
Mozell
10 months ago
Okay, let's see. Vague statements and generic titles make sense as bad attributes. But I'm not sure about the other one - is assigning blame really a bad thing? I'll have to double-check that.
ED
Eden
11 months ago
Hmm, this is a tricky one. I'm not sure if I should pick the opposite of the good attributes, or if there are other specific bad attributes I'm missing. I'll have to think this through carefully.
SH
Shayne
11 months ago
I think I know this one - vague statements, assigning blame, and generic titles seem like the clear bad attributes. I'll make sure to avoid those in my bug reports.
CA
Candida
5 months ago
One bug per report is key too!
LE
Lelia
5 months ago
Definitely! Clear reports help everyone.
ST
Stefania
6 months ago
Generic titles make it hard to find issues later.
DO
Donte
6 months ago
Yes, and blaming others just creates tension.
AN
Antione
10 months ago
I agree! Vague statements really confuse things.