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.

Sign up for GitHub

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

Jump to bottom

utest does not allow for automated coverage reporting #4

Closed
niklarm opened this issue Dec 8, 2015 · 2 comments
Closed

utest does not allow for automated coverage reporting #4

niklarm opened this issue Dec 8, 2015 · 2 comments
Labels
closed_in_jira mirrored

Comments

@niklarm
Copy link
Contributor

niklarm commented Dec 8, 2015

The changes introduced to mbed-drivers here to enable coverage reporting require the use of the MBED_HOSTTEST_RESULT(result) macro.

However, in order to not have a dependency on mbed-drivers, utest implements this manually, which then does not trigger the end of the coverage report.

See ARMmbed/mbed-drivers#47 for information on moving test_env.h out of mbed-drivers.
@PrzemekWirkus
Copy link
Contributor

I will work on this :)

@ciarmcom
Copy link
Member

ARM Internal Ref: IOTSFW-2122

@niklarm niklarm mentioned this issue Mar 2, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed_in_jira mirrored
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@PrzemekWirkus @ciarmcom @niklarm