Timeline for What should I do when my defect is rejected?
Current License: CC BY-SA 3.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 3, 2017 at 6:36 | vote | accept | Natasha | ||
Nov 2, 2017 at 16:50 | answer | added | a Learner | timeline score: 0 | |
Nov 2, 2017 at 14:04 | comment | added | c32hedge | Learn about bug advocacy. See questions like How to sell a bug? and others. | |
Nov 2, 2017 at 12:48 | vote | accept | Natasha | ||
Nov 3, 2017 at 6:36 | |||||
Nov 2, 2017 at 12:16 | answer | added | NarendraR | timeline score: 2 | |
Nov 2, 2017 at 11:29 | history | edited | Kate Paulk | CC BY-SA 3.0 |
Cleaned up grammar, made clearer
|
Nov 2, 2017 at 10:48 | answer | added | Anand | timeline score: 2 | |
Nov 2, 2017 at 10:47 | comment | added | dbalakirev | I think you could refer the exact section of the specification that indicates what the application should do. Ideally, that is objective to show why you marked it a defect. | |
Nov 2, 2017 at 10:06 | comment | added | Sagar007 | See Natasha, As QA it is our responsibility to find and post bug with severity. Off the conventional flow, You can make conversation with Developer to resolve bug. If developer is not making it resolved then do not worry so much. You have completed your duty. If client will ask you then you can show the bug and also they can see who has reject it. :D So every time you win. | |
Nov 2, 2017 at 9:40 | review | Close votes | |||
Nov 2, 2017 at 11:29 | |||||
Nov 2, 2017 at 9:22 | comment | added | Patrick | Why has the developer rejected to resolve? | |
Nov 2, 2017 at 9:19 | review | First posts | |||
Nov 2, 2017 at 9:24 | |||||
Nov 2, 2017 at 9:19 | history | asked | Natasha | CC BY-SA 3.0 |