You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because toHaveBeenCalledExactlyOnceWith includes "exactly", this suggests that toHaveBeenCalledOnce actually checks for at least one call. But the documentation (and implementation) explain that both check for exactly one call. This naming discrepancy is misleading at best. I don't have an opinion about which is preferrable.
The text was updated successfully, but these errors were encountered:
jeengbe
changed the title
Inconsistent Naming: toHaveBeenCalledOnce vs toHaveBeenCalledExactlyOnceWith
Inconsistent Naming: toHaveBeenCalledOnce vs. toHaveBeenCalledExactlyOnceWithJan 11, 2025
Because
toHaveBeenCalledExactlyOnceWith
includes "exactly", this suggests thattoHaveBeenCalledOnce
actually checks for at least one call. But the documentation (and implementation) explain that both check for exactly one call. This naming discrepancy is misleading at best. I don't have an opinion about which is preferrable.The text was updated successfully, but these errors were encountered: