Timeline for Who is responsible for pinpointing bugs?
Current License: CC BY-SA 3.0
30 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Dec 25, 2020 at 13:49 | history | bounty ended | alecxe | ||
| S Dec 25, 2020 at 13:49 | history | notice removed | alecxe | ||
| S Dec 17, 2020 at 23:00 | history | bounty started | alecxe | ||
| S Dec 17, 2020 at 23:00 | history | notice added | alecxe | Reward existing answer | |
| Jan 5, 2018 at 11:42 | comment | added | alecxe | @VishalAggarwal it is mixed depending on how well a particular tester knows a product under test and other conditions. More often it is black and gray than white. Thanks. | |
| Jan 5, 2018 at 9:07 | comment | added | Vishal Aggarwal | Are you talking about black box or white box testing? | |
| Jan 5, 2018 at 9:04 | answer | added | Vishal Aggarwal | timeline score: 1 | |
| Sep 14, 2017 at 16:54 | comment | added | Peter M. - stands for Monica | @TomTom - you are right, It is neither developer or tester's choice. This is EXACTLY why we have managers to allocate resources like people's time. They are paid to know which group has more resources and which resources should be used to solve which problems for company as a whole. | |
| Sep 14, 2017 at 14:36 | history | protected | Bharat Mane♦ | ||
| Sep 14, 2017 at 12:57 | comment | added | TomTom | It is not the developers choice. Is it ethical to waste client resources? Is it ethical to bill more because you don't want to put more work to other lower paid assets that have exactly this job? I would argue a developer wasting his time is committing fraud. A tester is there exactly for this type of work. Nothing "polite" about wasting money and refusing to let a guy hired for a specific job make his job. | |
| Sep 14, 2017 at 12:34 | comment | added | alecxe | @TomTom right, you have a fair point there. Though, it is not quite ethical for a developer to use the "amount of money his fellow colleague/tester earns" fact to avoid taking more time to pinpoint a problem - it's probably very context-specific..but Peter, I think, summarizes it nicely - it's about being polite and diplomatic..and, yes, we have managers to deal with these conflict situations. Thanks. | |
| Sep 14, 2017 at 9:27 | comment | added | TomTom | "Sometimes, that is because this developer does not value tester's time as much as he or she values developer's time (which is not a healthy thing to have in a team)" Cough. You mean like the tester in 99% of the cases being paid less than the developer? It is totally sane to put more workload on the lower hourly cost side and free the more expensive resource to do more work that the lower paid resources can not do. People are NOT all equal, in terms of payroll. | |
| Sep 14, 2017 at 8:18 | comment | added | PlasmaHH | "hat is because this developer does not value tester's time as much as he or she values developer's time" in a lot of companies this is even reflected in the payroll and encouraged by management. I personally often like having the users of a software figure out more of the circumstances because they use it more, while I write the code more, they have a quite different perspective. Also I am constantly overloaded with work and if the goal is to fix bugs, then its worth more have someone look deeper into it instead of trying to find another that will wait in the queue anyways. | |
| Sep 14, 2017 at 3:43 | comment | added | Joshua | There's simply no general way to decide. Sometimes it's the user's antivirus. | |
| Sep 13, 2017 at 18:26 | comment | added | Xiong Chiamiov | Ideally the QA engineer and developer will huddle around one computer and isolate the bug together. | |
| Sep 13, 2017 at 18:20 | comment | added | Peter M. - stands for Monica | @alecxe Answers are easy. Asking good question makes half of the answer. :-) | |
| Sep 13, 2017 at 15:42 | answer | added | Cronax | timeline score: 3 | |
| Sep 13, 2017 at 15:41 | comment | added | alecxe | @PeterMasiar and I would absolutely give you a special badge for providing high-quality answers! Learned a lot from your answers. | |
| Sep 13, 2017 at 15:26 | comment | added | Peter M. - stands for Monica | @alecxe - I am not sure if there is a badge for asking good questions, but it should should be, and you rightly deserve it. | |
| Sep 13, 2017 at 13:50 | answer | added | Inky1980 | timeline score: 1 | |
| Sep 13, 2017 at 10:14 | answer | added | Nawshad Rehan Rasha | timeline score: 3 | |
| Sep 13, 2017 at 1:30 | history | tweeted | twitter.com/StackSQA/status/907778434356662272 | ||
| Sep 12, 2017 at 23:04 | vote | accept | alecxe | ||
| Sep 12, 2017 at 20:30 | answer | added | MrWonderful | timeline score: 9 | |
| Sep 12, 2017 at 17:46 | answer | added | dzieciou | timeline score: 14 | |
| Sep 12, 2017 at 17:18 | answer | added | Joe Strazzere | timeline score: 7 | |
| Sep 12, 2017 at 16:12 | answer | added | Peter M. - stands for Monica | timeline score: 26 | |
| Sep 12, 2017 at 15:58 | comment | added | i'i'i'i'i'i'i'i'i'i | I think a good way around this is to document the steps you took to achieve this state. The best way I've found of doing this is to use a screen sharing recording to demonstrate exactly how the bug is encountered. And of course, include as much details as possible e.g browser, OS etc. You could also have a template in which you fill out every time a bug is logged for consistency of reporting. | |
| Sep 12, 2017 at 15:52 | history | edited | alecxe | CC BY-SA 3.0 |
edited title
|
| Sep 12, 2017 at 15:47 | history | asked | alecxe | CC BY-SA 3.0 |