Welcome to the Gallery – a place where you'll find hope and strength through the healing power of art and the universal reach of technology –
a place where you can
Connect, Create, and Thrive!
Interested in partnering with us?
Click here to find out how!
Displaying (1) Comments | Comment on this piece | Report objectionable art
There is much software that suilppes value to people that is, actually, very bad software.Bad to you, perhaps. Bad to the customer, maybe. Or in a more nuanced way of looking at it, there are things that support its value to the customer, and things that threaten its value to the customer. The tester's role, like that of the critic, is to use our knowledge of the product, its context, and the audience and to identify those things.It seems to me that a lot of context-driven software testing does not examine software itself, but instead is forced only to consider any available value that people can be coaxed to realize from the software.I'd consider that to be a pretty serious mischaracterization of what context-driven testing is about. What have you seen or heard to suggest it?if the software cannot be made to have 100% unit test coverage, then it is by definition bad, and the work that faces us is to change the software so as to make it good, and the definition of good is to implement a design so as to achieve 100% unit test coverage.I think that's a terribly simplistic view; not only unagile, but also unAgile if we use the Manifesto as a rubric. There's a big difference between bad and not as good as it might be . It might be okay to say, that's a bad attribute of the software . Yet a piece of software can perfectly satisfy a customer without having 100% unit test coverage and the Manifesto is explicit that we value working software over comprehensive documentation . We as software testers have an appalling lack of available critical stances to adopt from which to actually examine the software itself.I don't think that's true at all. We have an infinity of stances available. The problem, as I see it, is that the stances are available but the in general, the craft appears not to opt for them. The context-driven community exists largely with the goal of recognizing precisely that point. Michael B.
By: | Dec 16, 2012 | Report Comment
All Board
Mr. B
There are 10 pieces of art in this thread