[asterisk-users] Asterisk Test Suite error

[upendra]

Hi Matthew ,


i have enabled the framework and tested the script, after running i am
getting some FAILS


-> tests/channels/SIP/refer_replaces_to_self --- FAILED

--> tests/channels/SIP/sip_tls_call --- FAILED

--> tests/channels/SIP/sip_cause --- FAILED

--> tests/masquerade --- FAILED


let me know still what i am missing in the testsuite.


Regards
Upendra



On Thu, Sep 6, 2012 at 6:41 PM, Matthew Jordan <mjordan at digium.com> wrote:

>
>
> ----- Original Message -----
>
> > From: "upendra" <uppi.me at gmail.com>
> > To: "Asterisk Users Mailing List - Non-Commercial Discussion"
> > <asterisk-users at lists.digium.com>
> > Sent: Thursday, September 6, 2012 2:22:24 AM
> > Subject: [asterisk-users] Asterisk Test Suite error
>
> > Hi,
>
> > i am trying to install the Asterisk test suite on my ubuntu system ,
> > i have followed all the installlation steps as mentioned in the link
> > (
> > http://blogs.asterisk.org/2010/04/29/installing-the-asterisk-test-suite/
> > ) , but when i am trying to run the script some of the test cases
> > are PASSED and most of them are FAILED and SKIPPPED. So please help
> > me out to do the testing correctly.
>
> > The following is the test report i got after running the script.
>
> <snip>
>
>
> There is newer documentation on the Asterisk wiki:
>
>
> https://wiki.asterisk.org/wiki/display/AST/Asterisk+Test+Suite+Documentation
>
> There are pages that describe how to install and run the Test Suite under
> that
> page.
>
> Skipped tests happen when you are missing a dependency that the test needs
> to
> run.  If you look at a verbose report for each test (which should also be
> output
> when the test run finishes), it should tell you what dependency was
> missing.
>
> Most of your failed tests appear to be those that require the
> TEST_FRAMEWORK
> compile time option in Asterisk.  You can enable that in menuselect when
> you
> have configured Asterisk with --enable-dev-mode.
>
> Those tests *should* have picked up the fact that the TEST_FRAMEWORK wasn't
> enabled and should have been skipped (so long as the Asterisk directory
> that
> the Test Suite is sitting in has that option enabled in its build options),
> but there is a known bug with those test's YAML configuration that is
> preventing
> them from picking up the TEST_FRAMEWORK flag.  Until we can get that
> cleaned up,
> enabling the TEST_FRAMEWORK flag should resolve that problem.
>
> --
> Matthew Jordan
> Digium, Inc. | Engineering Manager
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> Check us out at: http://digium.com & http://asterisk.org
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>                http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20120918/341eb7c9/attachment.htm>