Skip to content
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

Unit test target and logic test target #7

Open
otusweb opened this issue Jun 1, 2015 · 1 comment
Open

Unit test target and logic test target #7

otusweb opened this issue Jun 1, 2015 · 1 comment

Comments

@otusweb
Copy link

otusweb commented Jun 1, 2015

In our project we have two test targets. One is a unit test target and the other one a logic test target. The unit test target does not run the application and the gcda files for this target are saved in the unit_test.build by Xcode. On the other hand the logic test target gcda files are saved within the application build folder.

So when the plugin parses the gcda files to generate the code coverage, it misses the unit test information.
In the build_var file, object_file_dir is set to application.build/Objects-normal/x86_64
What can i do for the plugin to see both source of bcda files?

@tylermann
Copy link
Contributor

Hmm, so it sounds like you are having trouble generating gcov files for both builds? The plugin expects there to be gcov files already generated. It will then attempt to automatically find them, or you can manually set the folder that contains the gcov files and it will recursively search in that folder for them.
However, in the TestApp/build_scripts folder I have some sample scripts that can help generate .gcov files for you (which is I think the build_var file you are referencing) although they are just meant to be used as an example since everyone's build setup can be very different. It sounds like the easiest thing for you to do might be to slightly tweak the build_scripts to handle exporting more than one directory that contain .gcda files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants