1cbd2db621
stdout/stderr now captured by junitxml
2013-04-16 00:45:14 -04:00
76fb51a4ba
fix issue 271 - dont write junitxml on slave nodes
2013-03-24 20:43:25 +01:00
dca5fa2241
fixing links for 2.3 release, and fixing a windows32 failure on py3
2012-10-19 10:53:28 +02:00
39b8a19cf7
Fix test for windows
2012-10-08 13:42:31 +02:00
848c749d1a
adapt the junit xml escaping test to my escaping changes
2012-09-03 09:54:02 +02:00
a6060dfb6d
use py3 compatible print syntax
2012-08-28 16:37:43 -04:00
1446b4b4e6
fix issue #178 and extend the failure escape test
2012-08-17 16:08:08 +02:00
172505f703
fix/consolidate --junitxml=path construction with relative pathes
2012-08-04 10:33:43 +02:00
6e0c30d67d
fix skip/xfail confusion, reported and discussed on
...
http://stackoverflow.com/questions/11105828/in-py-test-when-i-explicitly-skip-a-test-that-is-marked-as-xfail-how-can-i-get
2012-06-23 11:32:32 +02:00
0790f7a75f
fix issue 144 - wrong classname in junitxml
2012-05-22 17:18:04 +02:00
1c817aa7bd
don't use octal syntax, since its not py2/py3 compatible
2012-04-18 11:26:44 -04:00
ee8d2f9950
junitxml: use a exclusive match on the legal ranges of xml for binary escaping, fixes issue 126
2012-03-09 13:12:18 +01:00
703da22831
put systemout/systemerr to correct xml location
2011-07-13 18:47:27 +02:00
f3bc197afb
fix #59 : provide better Jenkins stdout and stderr sections
2011-07-12 23:09:03 +02:00
5e311d3bfc
fix timing float comparison
2011-05-29 00:45:31 +02:00
5498fe960f
add another normpath in the junitxml tests
2011-05-28 19:00:23 +02:00
4c885cf0d2
hopefully final win32 fix for the junitxml path expansion
2011-05-28 17:36:38 +02:00
70dc7a976d
dont wrap comparisation paths in py.path.local for the junitxml tests, since missing $HOME causes issues else
2011-05-28 16:52:05 +02:00
8dc4e732f0
fix issue47 - fix time-per-test timing output for junitxml
2011-05-28 14:03:10 +02:00
56b40ebd75
use os.path.expanduser/expandvars on the junitxml path for convience, fixes #44
2011-05-27 07:54:03 +02:00
1c1918eb22
Prevent null-characters from appearing in junitxml's output
...
The Jenkins XML parser does not deal with null-characters inside the
XML. This replaces any null character with nothing in the XML output,
which makes no visual difference.
2011-04-16 00:09:25 +01:00
3a9788fc6f
fix missing reason/name information for skipped tests
2011-03-19 17:59:07 +01:00
a698465487
streamline docs, especially use "import pytest" and "pytest.*" in python code examples instead of "import py" and "py.test.*".
2010-11-17 22:12:16 +01:00
076e03e90f
also un-nest test directory
2010-11-13 11:30:40 +01:00
Adam Goucher
Ronny Pfannschmidt
holger krekel
Benjamin Peterson
Floris Bruynooghe