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
I reviewed the README file to see if the feature is in the major future work.
I performed a cursory search to see if the feature request is relevant, not redundant, nor in conflict with other tickets.
Is your feature request related to a problem? Please describe.
FM divides its coverage test into separate units and uses stubs for all units other than the unit under test. However, this appears to be a mixture of hand-written and some generated stubs, and the hand written stubs can diverge from the implementation.
Describe the solution you'd like
Re-run the UT assert generate stubs script and use the generated stubs only.
Additional context
This makes the UT stubs easier to maintain - any time a header file changes, just re-run the tool and re-commit the stubs. It is best not to modify the generated stub in any way, if it can be avoided.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Checklist (Please check before submitting)
Is your feature request related to a problem? Please describe.
FM divides its coverage test into separate units and uses stubs for all units other than the unit under test. However, this appears to be a mixture of hand-written and some generated stubs, and the hand written stubs can diverge from the implementation.
Describe the solution you'd like
Re-run the UT assert generate stubs script and use the generated stubs only.
Additional context
This makes the UT stubs easier to maintain - any time a header file changes, just re-run the tool and re-commit the stubs. It is best not to modify the generated stub in any way, if it can be avoided.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: