river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Costers (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-333) Tested platforms
Date Sat, 28 Aug 2010 12:13:53 GMT

    [ https://issues.apache.org/jira/browse/RIVER-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903817#action_12903817

Jonathan Costers commented on RIVER-333:

I am experimenting with having the QA harness generate HTML reports from the tests it is running.
This seems to be working very well.

This would have a couple of advantages:
- it spells out the platform parameters (OS, JVM) that it has run the tests on
- test output and logging is written to separate files per test, easily browsable
- detailed output from every test is no longer sent to the console
- zipping the whole reports directory and emailing that to river-dev would be a way to gather
test results from a variety of platforms

I am currently running the complete suite we have setup for qa.run with this option enabled.
As soon as it finished, I will post a sample of the HTML reports here.

> Tested platforms
> ----------------
>                 Key: RIVER-333
>                 URL: https://issues.apache.org/jira/browse/RIVER-333
>             Project: River
>          Issue Type: Test
>          Components: other
>    Affects Versions: AR3
>         Environment: All
>            Reporter: Peter Firmstone
> Currently we have dependencies on Sun proprietary API in both the testing suite and in
Phoenix, this makes it difficult to test on a wide variety of Java platforms.
> It would be desirable to have an ant task that checks and records the platform being
tested during a build so a developer can submit all test results in an easily uploadable archive
that is named after the Apache Release and Platform.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message