mockito
Avoid duplicate verbose logs across verification callbacks
While working on PR #1803 to stop duplicate verbose logs during verification, we discovered that the current approach is brittle because it depends on method timing and naming.
Proposal I’d like to discuss a design that avoids duplication across listeners entirely. Instead of detecting verification calls by name/timing, we could: – Track invocation events and mark those triggered by verification callbacks. – Ensure the VerboseMockInvocationLogger is called only for real method invocations.
Goal Arrive at a stable solution for de-duplicating verbose logging across listeners without relying on brittle timing checks.
Please advise on feasibility or alternative directions before we start implementing.
We’re a small university group contributing to Mockito as part of a software engineering course project. This issue looks clear and manageable, and we’d like to take it if it’s still available. Please let us know if it’s okay for us to proceed — thanks!
