[OWASP_PHPSEC] Code Coverage along with unit testing
sven at rtbg.de
Fri Apr 11 15:27:23 UTC 2014
I've written it in a message before, here is what I did for my own account:
It's two easy steps:
1. Go to https://coveralls.io and sign in with Github
2. After they synced the repositories and show them, set OWASP/phpsec to on.
Am 11.04.2014 17:24, schrieb Abbas Naderi:
> What do I need to do?
> Notice: This message is digitally signed, its source and integrity are verifiable.
> If you mail client does not support S/MIME verification, it will display a file (smime.p7s), which includes the X.509 certificate and the signature body. Read more at Certified E-Mail with Comodo and Thunderbird in AbiusX.com
> On Apr 11, 2014, at 7:21 AM, Sven Rautenberg <sven at rtbg.de> wrote:
>> I merged the configuration for this, but haven't been able to add the
>> repo at the coveralls.io site. I simply lack the rights to do it.
>> But I'd very much like to see code coverage statistics! @Abbas: Looks
>> like this is your task. You did something similar with TravisCI integration.
>> Am 08.04.2014 00:00, schrieb Minhaz A V:
>>> Hello everyone,
>>> I have integrated coveralls in my forked version of phpsec, & its working
>>> nice giving code coverage with every commits, pull requests etc.
>>> I think its good to have code coverage with CI, for open source projects.
>>> Also with phpsec being in gsoc this year, it'd help the candidate to keep
>>> track of how much code has been covered & how much left.
>>> I have sent a pull for this https://github.com/OWASP/phpsec/pull/93.
>>> I'd like to know about your opinions on this.
>>> OWASP_PHP_Security_Project mailing list
>>> OWASP_PHP_Security_Project at lists.owasp.org
>> OWASP_PHP_Security_Project mailing list
>> OWASP_PHP_Security_Project at lists.owasp.org
More information about the OWASP_PHP_Security_Project