Conflict almost always arises through bad communication. If by user for example you mean tester, then perhaps we can better answer your question. But if you mean user as in end user, of the product, then I would be surprised they come into conflict with each other.
One of the roles as I see it of a tester is to be pedantic, for example if in the tech spec, or user requirements, it states "click button A to print report. " Then that is what must happen. There is a bug if a) the report is printed without clicking and b) if clicking doesn't print a report.
Now how do we communicate this to the developer? If you say hey your program is bugged it doesn't work, then you are likely to have a conflict. If you say, Hi, on page 3 paragraph 4, user requirement XXX, it states we must click button to have report, But in fact this is not the case, then your are more likely to make headway! |
