Comments on: More and Better Test Ideas http://thetesteye.com/blog/2009/05/more-and-better-test-ideas/ by rikard edgren, henrik emilsson and martin jansson - with torbjörn ryber and henrik andersson Thu, 17 May 2012 16:53:59 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Rikard Edgren http://thetesteye.com/blog/2009/05/more-and-better-test-ideas/comment-page-1/#comment-145 Rikard Edgren Wed, 24 Jun 2009 11:22:13 +0000 http://thetesteye.com/blog/?p=296#comment-145 Wiki is probably a good thing for things like this (I normally "own" my test ideas, so I use Word.) Another difficulty I believe is how to make sure you get feedback. Some people like the format (one-liners) better than others. Wiki is probably a good thing for things like this (I normally “own” my test ideas, so I use Word.)
Another difficulty I believe is how to make sure you get feedback. Some people like the format (one-liners) better than others.

]]> By: Martin Jansson http://thetesteye.com/blog/2009/05/more-and-better-test-ideas/comment-page-1/#comment-139 Martin Jansson Thu, 18 Jun 2009 07:17:21 +0000 http://thetesteye.com/blog/?p=296#comment-139 One big challenge around these test ideas is how to incorporate them in our daily work. I've tested several different methods around this and it can be hard to avoid redundant documentation. Transfering test ideas or refering to them from a test case can lead to that the tester must cross-reference continuously and slow down his work. The best environment so far has been when using a wiki for these test ideas, where you do not refer to individual test ideas but instead whole sections. This means that the section can continually grow and change. I guess this could be a separate paper. It is better to just start working on them instead of getting stuck in how to structure them. One big challenge around these test ideas is how to incorporate them in our daily work. I’ve tested several different methods around this and it can be hard to avoid redundant documentation. Transfering test ideas or refering to them from a test case can lead to that the tester must cross-reference continuously and slow down his work.

The best environment so far has been when using a wiki for these test ideas, where you do not refer to individual test ideas but instead whole sections. This means that the section can continually grow and change.

I guess this could be a separate paper. It is better to just start working on them instead of getting stuck in how to structure them.

]]>