[Ns-developers] Unit Tests

[Mitch Watrous]

What happens if you do test.py without any arguments like this:

     ./test.py

Mitch

On 11/17/2011 12:55 AM, Andrea Sacco wrote:
> Hi Mitch,
>
>> Those test.py options work on my machine, which is Fedora Core 14.
>>
>> What operating system are you using?
> I'm running ns-3-dev on Ubuntu 11.10 (Virtual Box Machine)
>
>> What happens when you run test.py?
> socket at socket-laptop:~/repos/ns-3-allinone/ns-3-dev$ ./test.py -c core
> Waf: Entering directory `/home/socket/repos/ns-3-allinone/ns-3-dev/build'
> Waf: Leaving directory `/home/socket/repos/ns-3-allinone/ns-3-dev/build'
> 'build' finished successfully (6.957s)
>
> Modules built:
> aodv                      applications              bridge
> config-store              core                      csma
> csma-layout               dsdv                      emu
> energy                    flow-monitor              internet
> lte                       mesh                      mobility
> mpi                       netanim                   network
> nix-vector-routing        olsr                      point-to-point
> point-to-point-layout     propagation               spectrum
> stats                     tap-bridge                template
> test                      tools                     topology-read
> uan                       virtual-net-device        visualizer
> wifi                      wimax
>
> Modules not built:
> click                     openflow
>
> 0 of 0 tests passed (0 passed, 0 skipped, 0 failed, 0 crashed, 0
> valgrind errors)
>
> I get the same if I run test.py with the -c unit switch.
>
> The only "tests" I'm able to run are examples, with the -c example
> switch, which runs 72 examples, all passed..
>
> Thanks,
> Andrea