-
-
Notifications
You must be signed in to change notification settings - Fork 16
Introduce mock testing #32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
v3.0.0
v3.0.0
v3.1.2
e7aaa32
to
198c0ee
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I factored out #33 from this PR to avoid mixing the mocking (which is still WIP and probably needs some time) with the upgrade to preCICE v3 (which is pretty much ready to merge).
Regarding the mocking: General approach looks good.
Will briefly summarize what todos we discussed yesterday in order to keep @IshaanDesai in the loop:
- put mocked implementation into dedicated folder (e.g.
testing/mock/fluent
) - split
mockedFluent.c
intotesting/mock/fluent/udf.h
andtesting/mock/fluent/dynamesh_tools.h
- automatize selection of mocked vs. non-mocked Fluent. There are two possible approaches:
- Use macros to switch between the real
#include "udf.h"
and the mocked#include "testing/mock/fluent/udf.h"
. - Always use
#include "udf.h"
and pick the real/mocked version by selecting the respectivemakefile
with the corresponding include paths.
- Use macros to switch between the real
@khalilhkiri please comment if I forgot any important points.
v3.1.2
Shall I have a look or this is still WIP? |
it s still WIP, needs some more adjustments |
No description provided.