What are some adjectives while reporting any issues?
I am working as a QA in a private firm. I report the issues in a defect tracking tool. I am searching some adjectives related to the issues that I find. e.g. On a website a there are number of tabs each tab shows different page. Suppose one tab doesn’t show the contents on the page. So, I will write in the summary as, Tab ABC looks fishy. or ABC tab has a glitch. Can you give list of objectives or some best sentences so that I can use them in Summary or description of the issues?
Observing members:
0
Composing members:
0
8 Answers
I always liked using FUBAR. (F’d up beyond repair)
Are you only looking for words that describe a page that doesn’t show the contents? If so you could use the words blank or missing or information is missing or isn’t showing or isn’t showing up, or the information has been compromised, or the information is incorrect, or the information is incomplete.
I’ve always liked PEBKAC—Problem Exists Between Keyboard And Chair. In short, user error.
@kardamom: If I have to submit an issue from a game which has all animations not in a proper alignment. So I can make the sentence in bug summary that, “The animations are wonky” instead of Animations are not in alignment”.
@Cruiser :If I use that word, I will be kicked out from the company. :).
Why are you looking for these types of general things to say instead of what is actually going on? It seems to me that ABC Tab is missing conveys more information that ABC tab is wonky.
Just be plain ol’ descriptive.
I have to agree with @marinelife that wonky is subjective, but tabs ABC are missing is specific and accurate.
Words like wonky and hinky and screwed up just don’t tell the reader of the summary what the specific problem is.
Plain and descriptive is best:
missing
inaccurate
garbled
ambiguous
unreadable
Answer this question
This question is in the General Section. Responses must be helpful and on-topic.