Re: [Tikiwiki-devel] Test error/failure on Tiki6

[Stephane C. <se...@lo...>]

Le Thu, Nov 11, 2010 at 11:09:49AM +0100, cha...@gm... écrivait :
> ################## 2 TEST FAILURES ##################
> TikiImporter_Test::testChangePhpSettings
> Should change the value of max_execution_time
> Failed asserting that <string:0> matches expected <integer:360>.
> 
> in lib/test/importer/TikiImporterTest.php:29
> LanguageTest::testUpdateTransShouldNotUpdateTranslation
> Failed asserting that <string:1> matches expected <null>.
> 
> in lib/test/language/LanguageTest.php:99
> ################## 7 TEST ERRORS ##################
> LanguageTest::testUpdateTransShouldNotUpdateTranslation
> Failed asserting that <string:1> matches expected <null>.
> 
> in lib/test/language/LanguageTest.php:99
> LanguageTest::testUpdateTransShouldNotUpdateTranslation
> Failed asserting that <string:1> matches expected <null>.
> 
> in lib/test/language/LanguageTest.php:99
> LanguageTest::testUpdateTransShouldNotUpdateTranslation
> Failed asserting that <string:1> matches expected <null>.
> 
> in lib/test/language/LanguageTest.php:99
> LanguageTest::testUpdateTransShouldNotUpdateTranslation
> Failed asserting that <string:1> matches expected <null>.
> 
> in lib/test/language/LanguageTest.php:99
> LanguageTest::testUpdateTransShouldNotUpdateTranslation
> Failed asserting that <string:1> matches expected <null>.
> 
> in lib/test/language/LanguageTest.php:99
> LanguageTest::testUpdateTransShouldNotUpdateTranslation
> Failed asserting that <string:1> matches expected <null>.
> 
> in lib/test/language/LanguageTest.php:99
> LanguageTest::testUpdateTransShouldNotUpdateTranslation
> Failed asserting that <string:1> matches expected <null>.
> 
> in lib/test/language/LanguageTest.php:99

Hum doesn't seems right when comparing to the web page :(

failure 	TikiImporter_Test::testChangePhpSettings() 	
failure		LanguageTest::testUpdateTransShouldNotUpdateTranslation() 	
error 	Rating_RegisterVoteTest::testRecordUserVotes() Rating_RegisterVoteTest
error 	Rating_RegisterVoteTest::testAnonymousVotes() Rating_RegisterVoteTest
error 	Rating_RegisterVoteTest::testGetUserVote() Rating_RegisterVoteTest
error 	Rating_RegisterVoteTest::testGetAnonymousVote() Rating_RegisterVoteTest
error 	Rating_RegisterVoteTest::testEnvironmentUserLookup() Rating_RegisterVoteTest
error 	Rating_RegisterVoteTest::testEnvironmentAnonymousLookup() Rating_RegisterVoteTest
error 	Rating_RegisterVoteTest::testCannotRecordOnUnknownObjectType() Rating_RegisterVoteTest
 
BTW, what do we do about these "new" errors in quality:
 o Subversion property "svn:keywords" = "Id" does not match "Author Id Revision"
 o Missing Subversion property "svn:eol-style" = "native"

Why not for svn:keywords, but for svn:eol-style I think for the moment
the eol-style is unix, so what do we do ?

And what do we do for CSS errors/warnings for the moment there is to
much noise in these reports to be usefull for example:
   CSS colours must be defined in uppercase; expected #C1C2 but found #c1c2
should be ignored
same as
   Style definitions must be lowercase; expected verdana but found Verdana
As it is not errors in the CSS just different coding style

But
  Style definitions must end with a semicolon
might cause real pb and should be fixed...

So can we all agree on messages to be shown in quality and then
eradicated from the source ? ;p

So all could be done for 6.1 or trunk ?

A+
-- 
Stéphane Casset            LOGIDÉE sàrl       Se faire plaisir d'apprendre
1a, rue Pasteur        Tel : +33 388 23 69 77           ca...@lo...
F-67540 OSTWALD        Fax : +33 388 23 69 77           http://logidee.com