-
Notifications
You must be signed in to change notification settings - Fork 7
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
query re: code coverage #19
Comments
Can you elaborate on what you're trying to achieve? |
using code coverage to make sure I've got a gherkin snippet for all the test cases I've written in the plugin. |
note for reference: psalm/plugin-phpunit uses this module but doesn't have coverage enabled so I don't have a reference point to figure out what I'm doing wrong :s |
Hm, ok. I don't think it would be easy, if possible at all. What this module does, roughly, is this:
Since Psalm is run as an external binary, it's not imediately clear to me how to enable code coverage collection during its run, and how to get coverage data out of it. |
Possibly it could be done by running Psalm like this:
Where Alternatively, a modified copy of c3 (https://github.com/Codeception/c3) could be injected into Psalm environment. As there won't be any webserver running, it would have to be changed to communicate with Codeception by some non-HTTP means. |
The latter approach seem technically feasible:
|
@weirdan do you think it'd be more practical to re-open vimeo/psalm#3977 so one could just use phpunit ? |
This module's dependents may still benefit from having code coverage, so I plan to look into this anyway. |
Having a bit of a problem at the dayjob; have got this psalm module integrated with a plugin for tests, but getting 0% coverage despite tests passing.
Any ideas where I might go looking?
The text was updated successfully, but these errors were encountered: