-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Platform: All, OS: All
shows
"Standard Error
Skipping org.openide.filesystems.FileObjectTestHid.testWriteReadExclusion
Skipping org.openide.filesystems.FileObjectTestHid.testWriteReadExclusionDeadlock"
but this information, from SuiteResult, is not available in the corresponding
/api/xml.
I guess the problem is that what is exposed is a hierarchy of TestResult ->
PackageResult -> ClassResult -> CaseResult. The SuiteResult's most commonly
correspond to ClassResult's but this is not always true, and we would not want
to serialize a SuiteResult's info inside a CaseResult's output since this would
often create duplicate output.
Could perhaps have the root TestResult also enumerate SuiteResult's as a
separate subtree, with the serialized information being the name, duration,
timestamp, stdout/err, and perhaps list of CaseResult names for cross-linking?
Of course these names are not guaranteed to be unique. Ideally, the XML
structure would expose the CaseResult.parent -> SuiteResult links using e.g.
generated element IDs, but this may be beyond the capabilities of your XML
serialization framework.
- is duplicated by
-
JENKINS-2839 testReport/api/xml broken
-
- Closed
-
[JENKINS-2760] No stdout/stderr in XML API
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Link |
New:
This issue is duplicated by |
Status | Original: Reopened [ 4 ] | New: In Progress [ 3 ] |
Despite the possible performance problem, I think the easiest thing to do is to
expose stdout/err from CaseResult.
We might also want the URL that returns the raw JUnit XML that Hudson saves in
its file system. That is likely just as parse-able and have no duplication problems.