15 Commits

Author	SHA1	Message	Date
Willi Goesgens	bea60cf73b	If whole testsuite fails, create a new 'testcase' with the full message inside so we see the actualy problem in jenkins.	2014-09-29 09:51:25 +02:00
Willi Goesgens	5696c37c1b	If a whole test suite fails, output the global error message.	2014-09-26 17:16:08 +02:00
Willi Goesgens	815e39cb58	don't treat 'message' as testcase.	2014-09-26 09:43:07 +02:00
Willi Goesgens	705746ff87	Typo.	2014-09-25 16:07:27 +02:00
Willi Goesgens	cf72047b30	Catch exceptions from testing.js	2014-09-25 15:47:02 +02:00
Max Neunhoeffer	02d154aff6	Fix another typo.	2014-09-25 14:06:02 +02:00
Willi Goesgens	8df5b7e9d9	Catch exceptions and print informations to debug the tests.	2014-09-25 13:39:42 +02:00
Willi Goesgens	357764ac57	Implement structures in the same way for all other tests, and move the pretty printer over, so users calling testing.js directly can also enjoy human readable test results.	2014-09-23 16:56:24 +02:00
Willi Goesgens	968023aa46	Measure the time used per test.	2014-09-23 10:44:08 +02:00
Willi Goesgens	fd3931a99a	wrap error message in cdata section.	2014-09-22 18:21:08 +02:00
Willi Goesgens	e56aeb6fad	split unittest results into several xml files - each testsuite is one file.	2014-09-22 18:00:52 +02:00
Willi Goesgens	03ca3431e1	Add more information to the unittest status xml	2014-09-22 17:10:06 +02:00
Willi Goesgens	63be847a59	Output an XML status of the unittest which we hope is understood by Jenkins.	2014-09-12 15:45:47 +02:00
Max Neunhoeffer	84644a4c10	Report result of unittest in file.	2014-03-14 14:40:33 +01:00
Max Neunhoeffer	6a91ba63f2	Add a convencience script to run unittests as follows: ... scripts/run scripts/unittest.js all	2014-02-21 11:26:29 +01:00