History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-490
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Steve Luo
Reporter: AlSt
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Support JUnit reports containing several executions of the same JUnit test (cf. compatibility tests)

Created: 21/Dec/09 03:38 PM   Updated: 12/Jan/10 02:22 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: None
Image Attachments:

1. screenshot-1.jpg
(240 kb)

2. screenshot-2.jpg
(304 kb)
Environment: PMEase QuickBuild, 2.0.12, 2009-12-17


 Description  « Hide
See attached screenshots: We have a couple of critical tests (in this scenario just two) that must be executed with different versions of another component to check the compatibility. That is, one and the same test is executed several times. By specifying different report sub-folders the Ant JUnit HTML report task is able to more or less generate a useful report (note that the specialization in parentheses is due to an adaption of the default XSLT stylesheet).

Minimalistic requirement:
* Detect all executions of the same test (i.e. 44 instead of 2 tests in this scenario).

I don't dare to ask for a possibility to flag the tests e.g. via a System Property as we do it. Thus, we don't mind to nonetheless generate the default Ant JUnit HTML report with our XSLT adaptions, but currently the notifications and build summaries are quite confusing or rather misleading.

Note that in an aggregate Ant JUnit XML report there seems to be a unique id attribute for each test suite element:
  <testsuite errors="0" failures="0" hostname="lab13" id="1" name="ClassCacheTest" package="com.dynatrace.diagnostics.integrationtest.instrumentation" tests="1" time="43.066" timestamp="2009-12-21T14:00:39">

 All   Comments   Work Log   Change History      Sort Order:
No work has yet been logged on this issue.