Azure / Azure/umock-c

umock_c could print "from where" does a STRICT_EXPECTED_CALL comes from

Open
#69 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C
Stars
36
Forks
27
Avg merge
32m
Merged PRs (30d)
3

Description

I would like to have the "expected" calls be more verbose (for matching purposes) and would be awesome if the expected calls that were not matched by an actual call would also print their origin (`__LINE__` would do).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating how STRICT_EXPECTED_CALL records expected calls and where unmatched expected calls are printed. Trace the reporting path and confirm how __LINE__ could be retained; done means verbose output identifies the origin of each unmatched expected call and provides more matching detail.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.