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
{{ message }}
This repository has been archived by the owner on Jun 18, 2021. It is now read-only.
It seems the mocking part also uses a model, a pre-condition and a transition function, but instead of semantics and post-conditions it has a so called callout function. This callout function is what constructs the mocked return value from the model and the arguments to the mocked action.
How exactly this works and how it can be fit into our library is still not clear to me...
The text was updated successfully, but these errors were encountered:
In the paper Modelling of Autosar Libraries for Large Scale Testing a mocking framework is used to simplify the testing process. The framework is described in the paper An expressive semantics of mocking [PDF].
It seems the mocking part also uses a model, a pre-condition and a transition function, but instead of semantics and post-conditions it has a so called callout function. This callout function is what constructs the mocked return value from the model and the arguments to the mocked action.
How exactly this works and how it can be fit into our library is still not clear to me...
The text was updated successfully, but these errors were encountered: