aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Ross (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1258) Refactorings in subsystem tests
Date Fri, 26 Feb 2016 12:35:18 GMT

    [ https://issues.apache.org/jira/browse/ARIES-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168915#comment-15168915
] 

John Ross commented on ARIES-1258:
----------------------------------

I would hate to close this and give us an excuse to relax. It is indeed annoying how the generated
test files show up as changes. Perhaps an interim solution would be find a way to tuck those
files under the target or some other ignored directory. I'll just assign this to myself for
now to keep it off the open/unassigned list until I figure out what to do.

> Refactorings in subsystem tests
> -------------------------------
>
>                 Key: ARIES-1258
>                 URL: https://issues.apache.org/jira/browse/ARIES-1258
>             Project: Aries
>          Issue Type: Test
>          Components: Subsystem
>    Affects Versions: subsystem-2.0.6, subsystem-2.0.8
>            Reporter: Christian Schneider
>            Assignee: John Ross
>
> The subsystem tests currently use a mix of maven, ArchiveFixture and custom code to create
test subsystem esa files.
> I would like to replace this with TinyBundles.
> Advantages are:
> - We use the standard bundling tool of pax exam
> - The complete bundles and esa files can be created using TinyBundles so the code is
more cohesive as it happens in one place
> - When running the tests from eclipse the project dir is not littered with build artifacts
anymore



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message