[asterisk-bugs] [JIRA] Status Changed to Waiting for Development: (ASTERISK-20505) Migrate hashtest/hashtest2 to be unit tests
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Thu Oct 4 20:37:28 CDT 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton updated ASTERISK-20505:
------------------------------------
Status: Open (was: Triage)
> Migrate hashtest/hashtest2 to be unit tests
> -------------------------------------------
>
> Key: ASTERISK-20505
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20505
> Project: Asterisk
> Issue Type: Improvement
> Security Level: None
> Components: Utilities/General
> Reporter: Matt Jordan
>
> After making some innocuous changes in {{astobj2}}, Richard informed me that I broke the build.
> What? How could this be? I compiled with {{--enable-dev-mode} and everything!
> As it turns out, {{hasthtest}} and its slightly more evil cousin, {{hashtest2}}, still lurk in utilities. Because they are stand-alone applications, anything that they reference that in turn uses something in asterisk that they do not link with has to be declared in their translation units. Otherwise... no linky.
> When I added the call to {{ast_register_atexit}} into {{astobj2}}, this broke their build - and they aren't built by default.
> What's worse is that these are really unit tests for core data structures in Asterisk that - despite our best wishes - are still used extensively in important locations in Asterisk. And they are not executed as part of our continuous integration. Not good.
> This task is to take the meat of those two applications and turn them into sustainable, executable unit tests.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list