[
https://issues.apache.org/jira/browse/MILAGRO-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857108#comment-16857108
]
Giorgio Zoppi edited comment on MILAGRO-29 at 6/5/19 10:19 PM:
---------------------------------------------------------------
Please assign to me.
The current tests are mainly manual in test directory. We want to use lcov and
gcov to match the algoritm and use openssl for verify the crypto correctness
when it is possible. This will enable any change in case of platform,
endianess.
We will proceed in the following way:
- i branch to milagro_cmocka and when the tests are read i will pull request to
merge, meanwhile i will work on milagro_cmocka.
was (Author: giorgio):
Please assign to me.
The current tests are mainly manual in test directory. We want to use lcov and
gcov to match the algoritm and use openssl for verify the crypto correctness
when it is possible. This will enable any change in case of platform,
endianess.
In the past we have in production experienced problems with blowfish for
example.
> Refactor unit milagro-c unit test with CMocka.
> ----------------------------------------------
>
> Key: MILAGRO-29
> URL: https://issues.apache.org/jira/browse/MILAGRO-29
> Project: Milagro
> Issue Type: Improvement
> Components: Core Crypto Libraries
> Affects Versions: Milagro Crypto Library 0.1.0
> Environment: unix/win32
> Reporter: Giorgio Zoppi
> Assignee: John McCane-Whitney
> Priority: Major
> Fix For: Milagro Crypto Library 0.1.0
>
>
> Cmocka support for unit testing. For having a more clear enviroment of
> testing and
> support milagro-moderncpp-wrapper we need to use a testing framework for the
> C Library.
> The propose is to use cmocka that it has been used by the samba group.
> [https://www.samba.org/~asn/sambaxp_2018_andreas_schneider_cmocka.pdf]
> This will enable a better quality then the manual test framework that we have
> now and using lcov we will able to show the coverage and integration for
> third party application.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
