To tell somebody that he is wrong is called criticism. To do so officially is called testing.
[img]/images/graemlins/smile.gif[/img] [img]/images/graemlins/tongue.gif[/img] [img]/images/graemlins/grin.gif[/img] [img]/images/graemlins/grin.gif[/img] [img]/images/graemlins/grin.gif[/img]
I like the term to disappear from the IT landscape as testing implies its an absolute science where anyone who has worked a while in the industry realises its more a risk mitigation / minimisation exercise. In particular with large scale complex software the real code path test coverage is generally low with the focus applied to core and/or high risk areas.
I look at a programme of testing in terms of how much risk there was at the beginning versus how much risk there is after testing.