It means the king is under direct attack and cannot avoid being captured.
There are situations where you want to checkmate someone. May be in
debate or discussions or game but I find checkmate principle useful for
the bugs that I would raise against the Software.
I ask below questions before raising a bug
- Why do you think it is a bug?
- Are you reporting symptom or real problem?
- What supporting facts would help to justify reasons of declaring a bug?
- Is it reproducible?
- Reproducible steps are clear enough to help others to replicate?
- Is bug description provides clarity on bug and its consequences being present in application?
- Do you need to attach other reference document or screenshots?
- Are you attaching appropriate screenshots?
I would also check certain things before raising a bug
- If bug is already raised in bug tracking system?
- Are you giving enough justification while deciding the severity of a bug?
- Is it environmental, build, data or application related issue? Categorising bug would help us to get clear idea about bug.
- Are you working on the latest build?
- Is your test data valid and not expired?
- Is testing function of application still in development?
- Do you really understand the functionality under test?
I think tester’s effectiveness would be counted on helping developer to fix bugs rapidly.
I think the tester should apply the checkmate principle to avoid rejections for raised bug.
As we know we spend lot of efforts and time on finding bugs then it make lot of sense to avoid rejections that are the whole point.
