Commit graph

19 commits

Author SHA1 Message Date
Patrick Ohly 2b9fdd0675 nightly test: include Client::Sync::*::testTimeout in report
This test is a bit special because it is only run for the first source
and doesn't really talk to the server. The logic in resultchecker.py
missed that test because the invocation of "client-test --help" didn't
print that test for "vcard21". Fixed by ensuring that only "vcard21"
is active during the --help call.
2011-04-12 11:25:59 +02:00
Patrick Ohly f438e5327c nightly testing: show source test results sorted by time
The Client::Source tests were sorted by name. This was confusing
because it hides when a peer like a CalDAV server stops responding
after a certain test.

It is more intuitive to present the results in the order in which they
were run. This is accomplished by sorting by the sub-second modification
time of the corresponding .log files (in resultschecker.py) and keeping
that order (in generate-html.xsl).

A similar approach might also be useful for Client::Sync. Not done yet.
2011-04-12 11:25:09 +02:00
Patrick Ohly 3ad1911705 runtests.py: added Yahoo and Google CalDAV/CardDAV testing
Added separate Client::Source tests for Yahoo CalDAV/CardDAV
and Google CalDAV. Reporting the results needs to know that these
"servers" are local tests.

These tests can only be run if CLIENT_TEST_WEBDAV is set as
expected by WebDAVSourceRegister.cpp.
2011-04-01 18:26:37 +08:00
Patrick Ohly 5a4c91382c nightly testing: added a column for "network failure"
This column is useful to determine at a glance whether tests
failed because of something outside of our control. The value
is also shown for each single test.
2010-09-02 13:48:46 +02:00
Zhu, Yongsheng deee96a368 Testing: add 'known failure' support in nightly (MBC#2870)
When a failure is known and it should not be treated as
a 'failed' case. Instead, 'knownfailure' is used to indicate
it. Thus, a new testing status for each case is shown in
the nightly testing outputs.
2010-06-17 09:28:19 +02:00
Zhu, Yongsheng 0f36e5801b Testing: fix wrong link for calendar+todo issue (MBC #1397)
If the source type is 'calendar+todo' type, XML spec doesn't allow
'+' in the element tag. Thus the current solution is to replace
'calendar+todo' with 'calendar_todo'.

But this is not a good choice. Instead, escaped strings are used.
"_" is escaped to "__". "+" is escaped to "_-".
So firstly escape these 2 characters when generating nightly xml
documents and then unescape them when generating nightly html page.
2010-05-18 08:47:25 +02:00
Chen Congwu 3fb68fe84a resultchecker: wrote 'calendar_todo' as tag name for 'calendar+todo'
'+' is a special character in the tag name, let's avoid it.
2010-04-20 09:22:10 +08:00
Chen Congwu 837c0429c8 Testing: Fix no html report error (MB#8391)
Do not write 'parameter' property, as the value sometimes fails the XML parser.
Generate a default HTML report if the report failed to generate.
2010-01-22 16:34:54 +01:00
Chen Congwu d24433e06d Testing: result check
Do not grep 'valgrind' because 'valgrind' is not guranteed to run
2009-12-01 21:45:34 +01:00
Chen Congwu ed099f8413 Testing: A special case set has slightly differnt case name 2009-12-01 21:45:34 +01:00
Chen Congwu 40470e6ec6 Testing Result Check: check "okay" instead of "fail" because of possible crash
Now the check criteria is:
"sourcename::casename: okay \*\*\*"
if the string is not present, the test result will be failed.
2009-12-01 21:45:34 +01:00
Chen Congwu 9391fcdca9 Testing result checker: change the result checker grep criteria
The grep criteria to check the test result did not work for tests with
 combined source.
2009-12-01 21:45:34 +01:00
Chen Congwu 41d312c6f2 Testing: fix some issues for prebuilt test
1) use string.partiton instead of split
2) change to a proper dir if srcdir is not existed
2009-12-01 21:45:34 +01:00
Chen Congwu f76c20fa78 Testing: show evolution-prebuilt in html output(bug#7160)
Generate <source> tests for evolution and evolution-prebuilt;
Do not generate client test template until a <sync> tests is existed.
2009-12-01 21:45:33 +01:00
Zhu, Yongsheng 280e67bddc Testing: refine return code checkings(bug#6457)
when memory leaks occur, the return code should be '100'
but python on unix will re-encode it and put them in a high byte
in a 16-bit number.
2009-12-01 21:45:33 +01:00
Chen Congwu 950e9251c2 Testing: add valgrind check result and backend scan dir
Change failure to skip for google known failures
Change report title to have more acurate time information
2009-10-16 14:25:31 +02:00
Chen Congwu e532d35d87 Testing: add chroot information and library information in the report
Add library information in the report
Refine the test result check statement.
2009-09-15 14:05:26 +02:00
Chen Congwu 74226c36c5 Testing: Do not go on with checking test results if failed early because of compile error, etc. 2009-08-26 08:23:47 +02:00
Zhu, Yongsheng c234306473 The main purpose is to refine nightly test report.
1) extract test results from many result files and combine them
into a xml format file to summary each unit test status
2) use 'compare.xsl' to compare two days' result and generate
comparison result
3) generate more visiable html output file by nightly result
and comparison result to make tracking regressions easily
2009-08-24 15:18:47 +02:00