Situation: a defect was sent to a developer, who says it is not a defect but a feature. What will you do?

If a developer claims that the observed behavior is not a defect but a feature, you should:

1. Review the requirements and specifications to ensure that the behavior indeed matches the description.
2. Discuss with the developer why they consider it a feature — there might be a misunderstanding or changes in requirements.
3. If the specifications are ambiguous, involve a business analyst or product manager for clarification.
4. Record the final decision: if it is truly a feature, close the bug with a "not a bug" note; if it is a defect, continue working on fixing it.

This approach helps avoid conflicts and maintains transparency within the team.