I'm testing a trial product and will only be used in the demo. It's my first time testing in this kind project and I really feel very awkward in this situation. Most of the bugs I've found were due to developer didn't implement the code, e.g. data/format validation, take shortcut to simplify the implementation. I'm afraid that if I just let all the bugs go, customer might be able to catch a bug during the demo. But I cann't be too strict to fail all these test cases, since nobody want to spend time and money on a demo product. How should I handle this? Suggestion is appreciated. Thanks
Lynne brings up a good point. If the customer is going to be using the demo, then the bugs should be addressed if possible. If a sales person is going to be running the demo, it is possible to leave the bugs in, so long as the sales person knows what not to do.
As in any project, requirements should be well-defined. For the demo version, the product manager should decide which sub set of requirements should be implemented. Leaving this decision to the developers without any proper review and documentation may cause the users of this version (in presentation or evaluation) a lot of frustration...
Pete's got the right idea, make sure the sales person is aware of any bugs which might blow the demo. But get the essential ones fixed especially if they show up in a high profile area. If the customer is allowed to play with it, better get most of them taken care of.
Success is the ability to go from one failure to another with no loss of enthusiasm.
~ Winston Churchill ~
If you could draw the difference between 'Demo' and 'Prototype' it would be easier for you. You could get away with murder (the kind of things you have come across) with a prototype.
Setting the expectation is important and also is the product a custom built app. for the customer or is it a product for general sales ? What kind of relationship do you have with the customer ? Is it a cold call sales pitch ?
All these factors need to be kept in mind. I'd guess there is no simple answer without knowing all the facts. If you come from a school of thought that there should be no known defects before the product goes out of the door then this may seem odd. All said I'd guess it is OK if some of the questions are answered.
Log all defects. There's little purpose in testing if you don't log them. Leave up to others what needs to be fixed and what can be worked around in the demo.
Make sure whoever is doing the actual demo has gone thru it and is 100% aware of where the problems are. Any good salesperson can talk their way around problems or avoid them as long as they aren't taken by surprise in front of the prospective customer.