Comments on: The best bug tracking system. Don’t raise bugs, write an automated test! http://www.makinggoodsoftware.com/2010/02/23/the-best-bug-tracking-system-dont-raise-bugs-write-an-automated-test/ Sun, 05 Sep 2010 22:08:56 -0600 http://wordpress.org/?v=2.8.3 hourly 1 By: Eusebiu Blindu http://www.makinggoodsoftware.com/2010/02/23/the-best-bug-tracking-system-dont-raise-bugs-write-an-automated-test/comment-page-1/#comment-11481 Eusebiu Blindu Thu, 19 Aug 2010 14:21:28 +0000 http://www.makinggoodsoftware.com/?p=1231#comment-11481 How to raise a new bug http://bit.ly/cTGxdY How to raise a new bug http://bit.ly/cTGxdY

]]> By: Are you using too many technologies in your projects? The 7 anti-patterns for technologies, frameworks and other technicalities in software development. | Making Good Software | the leading lady http://www.makinggoodsoftware.com/2010/02/23/the-best-bug-tracking-system-dont-raise-bugs-write-an-automated-test/comment-page-1/#comment-8844 Are you using too many technologies in your projects? The 7 anti-patterns for technologies, frameworks and other technicalities in software development. | Making Good Software | the leading lady Thu, 17 Jun 2010 12:39:32 +0000 http://www.makinggoodsoftware.com/?p=1231#comment-8844 [...] The best bug tracking system. Don’t raise bugs, write an automated test! [...] [...] The best bug tracking system. Don’t raise bugs, write an automated test! [...]

]]> By: Auto-fix your bugs with UT and SBSE « Agile Project Manager http://www.makinggoodsoftware.com/2010/02/23/the-best-bug-tracking-system-dont-raise-bugs-write-an-automated-test/comment-page-1/#comment-8228 Auto-fix your bugs with UT and SBSE « Agile Project Manager Thu, 03 Jun 2010 21:28:36 +0000 http://www.makinggoodsoftware.com/?p=1231#comment-8228 [...] taught you to write unit test cases for all your code? She probably insisted that you should write a new test case for every reported bug? You probably wondered why, but still followed her advice like any dutiful [...] [...] taught you to write unit test cases for all your code? She probably insisted that you should write a new test case for every reported bug? You probably wondered why, but still followed her advice like any dutiful [...]

]]> By: Emily http://www.makinggoodsoftware.com/2010/02/23/the-best-bug-tracking-system-dont-raise-bugs-write-an-automated-test/comment-page-1/#comment-8106 Emily Tue, 01 Jun 2010 05:18:28 +0000 http://www.makinggoodsoftware.com/?p=1231#comment-8106 That's an interesting post. I don't think that automated tests would be a replacement for the whole bureaucratic procedure though - rather an useful addition making the bug reproduction easier. Don't forget that it requires the QA people to posses extra skills, too. That’s an interesting post. I don’t think that automated tests would be a replacement for the whole bureaucratic procedure though – rather an useful addition making the bug reproduction easier. Don’t forget that it requires the QA people to posses extra skills, too.

]]> By: Dathan http://www.makinggoodsoftware.com/2010/02/23/the-best-bug-tracking-system-dont-raise-bugs-write-an-automated-test/comment-page-1/#comment-7932 Dathan Fri, 28 May 2010 20:36:52 +0000 http://www.makinggoodsoftware.com/?p=1231#comment-7932 You could make a screencast demonstrating the bug. You could make a screencast demonstrating the bug.

]]> By: Who should write unit tests? | Soapbox Rants and Raves http://www.makinggoodsoftware.com/2010/02/23/the-best-bug-tracking-system-dont-raise-bugs-write-an-automated-test/comment-page-1/#comment-6078 Who should write unit tests? | Soapbox Rants and Raves Thu, 01 Apr 2010 05:14:38 +0000 http://www.makinggoodsoftware.com/?p=1231#comment-6078 [...] read another interesting article about bug tracking and system testing.  Think about this… rather than creating a problem ticket for issues found in system test, [...] [...] read another interesting article about bug tracking and system testing.  Think about this… rather than creating a problem ticket for issues found in system test, [...]

]]> By: Kevin http://www.makinggoodsoftware.com/2010/02/23/the-best-bug-tracking-system-dont-raise-bugs-write-an-automated-test/comment-page-1/#comment-5286 Kevin Sat, 27 Feb 2010 03:38:29 +0000 http://www.makinggoodsoftware.com/?p=1231#comment-5286 Why can't we do both? We use the already well understood bug tracking system to record the bug. And also create a test case to actually reproduce the bug. Infact, isn't that what is supposed to be done? Only the test case is written by the developer and not the tester. Ideally, if you are following TDD then you know you missed a test case and just add it to your tests. Why can’t we do both? We use the already well understood bug tracking system to record the bug. And also create a test case to actually reproduce the bug.

Infact, isn’t that what is supposed to be done? Only the test case is written by the developer and not the tester. Ideally, if you are following TDD then you know you missed a test case and just add it to your tests.

]]> By: Jigar shah http://www.makinggoodsoftware.com/2010/02/23/the-best-bug-tracking-system-dont-raise-bugs-write-an-automated-test/comment-page-1/#comment-5268 Jigar shah Fri, 26 Feb 2010 13:31:44 +0000 http://www.makinggoodsoftware.com/?p=1231#comment-5268 Yes, when a bug is discovered one should immidiately write a test case to fail it. But IMHO Bug tracking helps in maintaining history, output, (When started when ended.) And all other info at one place. (svn commits for bug, codereviews etc..) Its history which can be referred again. In Ideal and small (developer) world, Yes, Only good test should do the job. It save time. Yes, when a bug is discovered one should immidiately write a test case to fail it. But IMHO Bug tracking helps in maintaining history, output, (When started when ended.) And all other info at one place. (svn commits for bug, codereviews etc..) Its history which can be referred again.

In Ideal and small (developer) world, Yes, Only good test should do the job. It save time.

]]> By: Michal Huniewicz http://www.makinggoodsoftware.com/2010/02/23/the-best-bug-tracking-system-dont-raise-bugs-write-an-automated-test/comment-page-1/#comment-5266 Michal Huniewicz Fri, 26 Feb 2010 10:07:23 +0000 http://www.makinggoodsoftware.com/?p=1231#comment-5266 That's an interesting post. I don't think that automated tests would be a replacement for the whole bureaucratic procedure though - rather an useful addition making the bug reproduction easier. Don't forget that it requires the QA people to posses extra skills, too. That’s an interesting post. I don’t think that automated tests would be a replacement for the whole bureaucratic procedure though – rather an useful addition making the bug reproduction easier. Don’t forget that it requires the QA people to posses extra skills, too.

]]> By: links for 2010-02-26 | sashidhar.com http://www.makinggoodsoftware.com/2010/02/23/the-best-bug-tracking-system-dont-raise-bugs-write-an-automated-test/comment-page-1/#comment-5264 links for 2010-02-26 | sashidhar.com Fri, 26 Feb 2010 09:02:56 +0000 http://www.makinggoodsoftware.com/?p=1231#comment-5264 [...] The best bug tracking system. Don’t raise bugs, write an automated test! (tags: programming qa bugs automatedtesting software code tips) [...] [...] The best bug tracking system. Don’t raise bugs, write an automated test! (tags: programming qa bugs automatedtesting software code tips) [...]

]]>