Comments on: Systems outside the testing radar http://thetesteye.com/blog/2010/03/systems-outside-testing-radar/ 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: Martin Jansson http://thetesteye.com/blog/2010/03/systems-outside-testing-radar/comment-page-1/#comment-333 Martin Jansson Wed, 10 Mar 2010 14:48:48 +0000 http://thetesteye.com/blog/?p=843#comment-333 If the resource allocator had focus on the overall costs I think it would look differently. The test team could still be clear that they would be able to identify these kinds of errors on all development to lower cost (that is, if they are fixed by development). If the resource allocator had focus on the overall costs I think it would look differently. The test team could still be clear that they would be able to identify these kinds of errors on all development to lower cost (that is, if they are fixed by development).

]]> By: Saam http://thetesteye.com/blog/2010/03/systems-outside-testing-radar/comment-page-1/#comment-332 Saam Tue, 09 Mar 2010 23:48:19 +0000 http://thetesteye.com/blog/?p=843#comment-332 Interesting question. We could probably benefit from considering this to a much larger extent than is currently done. But just becasue we are able to find a bug somewhere doesnt automatically mean we benfit from finding it. Interesting question. We could probably benefit from considering this to a much larger extent than is currently done. But just becasue we are able to find a bug somewhere doesnt automatically mean we benfit from finding it.

]]> By: Henrik Emilsson http://thetesteye.com/blog/2010/03/systems-outside-testing-radar/comment-page-1/#comment-331 Henrik Emilsson Mon, 08 Mar 2010 22:41:53 +0000 http://thetesteye.com/blog/?p=843#comment-331 Good thoughts and great stories! I guess that if you had a risk-based approach to testing in such projects, it would not be prioritization amongst products/applications. Instead the test areas would have been selected according to the risk that the applications or functions imply which then might be exposed during testing; regardless of application type and size. But it is easy to forget this! It is important to look at testing projects from different angles, not only from a line organization point of view; which is so often the case. Good thoughts and great stories!

I guess that if you had a risk-based approach to testing in such projects, it would not be prioritization amongst products/applications. Instead the test areas would have been selected according to the risk that the applications or functions imply which then might be exposed during testing; regardless of application type and size. But it is easy to forget this!

It is important to look at testing projects from different angles, not only from a line organization point of view; which is so often the case.

]]>