Timeline for Looking for a faulty application for training
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Nov 4, 2012 at 17:33 | history | suggested | dzieciou | CC BY-SA 3.0 |
Improved formatting
|
| Nov 3, 2012 at 17:09 | review | Suggested edits | |||
| S Nov 4, 2012 at 17:33 | |||||
| Sep 12, 2011 at 21:30 | comment | added | testerab | @Joe I would actually award initiative points to any trainee tester who presented me with a list of already identified bugs :) Mind you, the next request from me would be "so, having found this, how could it help you decide where to look for new bugs?" | |
| Sep 12, 2011 at 19:03 | comment | added | Joe Strazzere | "I have thought about writing my own or hacking up a open-source app so I could add in my own bugs. I like the idea. The only thing that has stopped me from doing it is time and skill. Both of which I have in short supply" As is often the case, if you have money in sufficient supply, you could contract out the work and make up for your lack of time and skill. I'd love to see an Ad for "Be-buggers wanted"! | |
| Sep 12, 2011 at 18:52 | comment | added | Joe Strazzere | It's a good idea, but a publicly-available piece of software with a list of already-identified bugs has one big problem - once you get the list of existing bugs, any applicant or newbie tester will also be able to get that list of existing bugs. | |
| Sep 12, 2011 at 2:11 | history | answered | bryce | CC BY-SA 3.0 |