Hi Jakob,

Thanks a lot for your explanation!

Gtest FAQ recommends not to have a system-wide pre-compiled copy of gtest 
(https://code.google.com/p/googletest/wiki/FAQ#Why_is_it_not_recommended_to_install_a_pre-compiled_copy_of_Goog),
 so I compile gtest locally just before running sumo’s ./confiugre. Then I give 
its scripts/gtest-config to ./configure through --with-gtest-config, and SUMO 
compiles sumo/unittests/src/sumo-unittests; all test in it succeed. Thanks!

You were totally right about SUMO_HOME, I had it pointing to an old 
installation of SUMO. When I removed it, 'sumo/tests/runTests.sh -l -zen -b 
myjob' reports mostly success (Tests Run: 3453, Known Bugs: 26, Failures: 29). 
I’ll see what’s going on in 29 failures later.

Regards,
Alex




> On 2014 Dec 9, at 12:46, Jakob Erdmann <[email protected]> wrote:
> 
> Hello,
> to run the unit tests you execute sumo/unittests/src/sumo-unittests
> The test are only built if the executable 'gtest-config' is present on your 
> system (which should be the case if a recent version of gtest is installed).
> The tests in sumo/tests are run every night and usually only very few are 
> broken at any time.
> You can check the daily status at http://sumo.dlr.de/daily/ which today shows 
> lots of broken tests due to an error on my part but you will find that most 
> of them are green during the year (by checking the historical test results 
> for any given application) and I assume they will be 'green' again tomorrow.
> The error regarding the copyright clause suggests that the sumo revision you 
> used for testing does not match the revision of the  test suite. You should 
> be able to run those tests by executing sumo/tests/runTests.sh If the 
> environment variable SUMO_HOME is set it must point to the root directory of 
> the sumo installation/check-out (otherwise it will be set automatically)
> regards,
> Jakob
> 
> 2014-12-08 12:23 GMT+01:00 Alex Voronov <[email protected]>:
> Hi,
> 
> I’m trying to create a Homebrew (http://brew.sh) formula for SUMO 
> (https://github.com/Homebrew/homebrew-science/pull/1412).
> 
> To make sure that the compilation went well, I want to run the unit tests. 
> However, I can’t figure out how to run them… I found that ‘configure' can 
> produce something for unit testing, but it is always disabled. I guess I need 
> to give some parameter to --with-gtest-config ?
> 
> I can run texttest in ‘tests/', but a lot of them are broken, reporting a 
> difference in the copyright clause text, I guess these tests are not actively 
> maintained.
> 
> So, my question is: how to run tests on Linux and/or Mac?
> 
> Best Regards,
> 
> Alex
> 
> 
> 
> --
> Dr. Alexey Voronov
> Viktoria Swedish ICT AB
> https://www.viktoria.se/people/alexey-voronov
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> _______________________________________________
> sumo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/sumo-devel
> 

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
sumo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sumo-devel

Reply via email to